aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-03-16 23:15:08 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-03-16 23:15:08 +0000
commit787eba734be8e1fb8c5fdb101a02e826cccec3e9 (patch)
tree511dc9dc0fc8e2f04c2e4862eb9e8348ee87396a /src/backend/access/gist
parentec6550c6c06ba3a0cf4df31d1016aa8eb8716ddb (diff)
downloadpostgresql-787eba734be8e1fb8c5fdb101a02e826cccec3e9.tar.gz
postgresql-787eba734be8e1fb8c5fdb101a02e826cccec3e9.zip
When creating a large hash index, pre-sort the index entries by estimated
bucket number, so as to ensure locality of access to the index during the insertion step. Without this, building an index significantly larger than available RAM takes a very long time because of thrashing. On the other hand, sorting is just useless overhead when the index does fit in RAM. We choose to sort when the initial index size exceeds effective_cache_size. This is a revised version of work by Tom Raney and Shreya Bhargava.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions