aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-10-31 16:40:04 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-10-31 16:40:04 -0400
commit6980f817e83c242c29c84a44f1e1f09e566439b7 (patch)
tree1be215c7f96859a4e5f4324ae936021d4372b9e4 /src/backend/access/gist/gistvacuum.c
parent6743a878a4e9442a9846d8c270e5028e514d44f3 (diff)
downloadpostgresql-6980f817e83c242c29c84a44f1e1f09e566439b7.tar.gz
postgresql-6980f817e83c242c29c84a44f1e1f09e566439b7.zip
Stop btree indexscans upon reaching nulls in either direction.
The existing scan-direction-sensitive tests were overly complex, and failed to stop the scan in cases where it's perfectly legitimate to do so. Per bug #6278 from Maksym Boguk. Back-patch to 8.3, which is as far back as the patch applies easily. Doesn't seem worth sweating over a relatively minor performance issue in 8.2 at this late date. (But note that this was a performance regression from 8.1 and before, so 8.2 is being left as an outlier.)
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions