diff options
author | Peter Geoghegan <pg@bowt.ie> | 2024-11-04 11:04:30 -0500 |
---|---|---|
committer | Peter Geoghegan <pg@bowt.ie> | 2024-11-04 11:04:30 -0500 |
commit | b6558e4f837e5c8f923e405ef6ab957ac2bd095a (patch) | |
tree | 8bd7f1723d7ad7ee8e296ae4aeab7c18d6675f8a /src/backend/access/gist/gist.c | |
parent | 3c0fd64fec8ed6fa3987c33f076fcffbc3f268c3 (diff) | |
download | postgresql-b6558e4f837e5c8f923e405ef6ab957ac2bd095a.tar.gz postgresql-b6558e4f837e5c8f923e405ef6ab957ac2bd095a.zip |
nbtree: Remove useless 'strat' local variable.
Remove a local variable that was used to avoid overwriting strat_total
with the = operator strategy when a >= operator strategy key was already
included in the initial positioning/insertion scan keys by _bt_first
(for backwards scans it would have to be a <= key that was included).
_bt_first's strat_total local variable now simply tracks the operator
strategy of the final scan key that was included in the scan's insertion
scan key (barring the case where the !used_all_subkeys row compare path
adjusts strat_total in its own way).
_bt_first already treated >= keys (or <= keys) as = keys for initial
positioning purposes. There is no good reason to remember that that was
what happened; no later _bt_first step cares about the distinction.
Note, in particular, that the insertion scan key's 'nextkey' and
'backward' fields will be initialized the same way regardless.
Author: Peter Geoghegan <pg@bowt.ie>
Reviewed-By: Tomas Vondra <tomas@vondra.me>
Discussion: https://postgr.es/m/CAH2-Wz=PKR6rB7qbx+Vnd7eqeB5VTcrW=iJvAsTsKbdG+kW_UA@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions