aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlog.c
diff options
context:
space:
mode:
authorAlexander Korotkov <akorotkov@postgresql.org>2023-12-27 14:22:02 +0200
committerAlexander Korotkov <akorotkov@postgresql.org>2023-12-27 14:35:08 +0200
commit7e6fb5da41d8ee1bddcd5058b7204018ef68d193 (patch)
tree915e481c1049304294d5d1ed6881637565556d30 /src/backend/access/transam/xlog.c
parent06b10f80ba4db745f21847520b07b4ffad814313 (diff)
downloadpostgresql-7e6fb5da41d8ee1bddcd5058b7204018ef68d193.tar.gz
postgresql-7e6fb5da41d8ee1bddcd5058b7204018ef68d193.zip
Improvements and fixes for e0b1ee17dc
e0b1ee17dc introduced optimization for matching B-tree scan keys required for the directional scan. However, it incorrectly assumed that all keys required for opposite direction scan are satisfied by _bt_first(). It has been illustrated that with multiple scan keys over the same column, a lesser one (according to the scan direction) could win leaving the other one unsatisfied. Instead of relying on _bt_first() this commit introduces code that memorizes whether there was at least one match on the page. If that's true we know that keys required for opposite-direction scan are satisfied as soon as corresponding values are not NULLs. Also, this commit simplifies the description for the optimization of keys required for the current direction scan. Now the flag used for this is named continuescanPrechecked and means exactly that *continuescan flag is known to be true for the last item on the page. Reported-by: Peter Geoghegan Discussion: https://postgr.es/m/CAH2-Wzn0LeLcb1PdBnK0xisz8NpHkxRrMr3NWJ%2BKOK-WZ%2BQtTQ%40mail.gmail.com Reviewed-by: Pavel Borisov
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions