diff options
author | Peter Geoghegan <pg@bowt.ie> | 2025-05-02 17:50:58 -0400 |
---|---|---|
committer | Peter Geoghegan <pg@bowt.ie> | 2025-05-02 17:50:58 -0400 |
commit | 0f08df406822bfa697dbcabef55728a8cb3e7fdb (patch) | |
tree | 463fec3e2d1b435ebbf1e0f2d03fd28f3fc35425 /doc/src | |
parent | 1681a70df3d68b6f9dc82645f97f8d4668edc42f (diff) | |
download | postgresql-0f08df406822bfa697dbcabef55728a8cb3e7fdb.tar.gz postgresql-0f08df406822bfa697dbcabef55728a8cb3e7fdb.zip |
Avoid treating nonrequired nbtree keys as required.
Consistently prevent nbtree array advancement from treating a scankey as
required when operating in pstate.forcenonrequired mode. Otherwise, we
risk a NULL pointer dereference. This was possible in the path where
_bt_check_compare is called to recheck a tuple that advanced all of the
scan's arrays to matching values: its continuescan=false handling
expects _bt_advance_array_keys to have been called with a valid pstate,
but it'll always be NULL during sktrig_required=false calls (which is
how _bt_advance_array_keys must be called when pstate.forcenonrequired).
Oversight in commit 8a510275, which optimized nbtree search scan key
comparisons.
Author: Peter Geoghegan <pg@bowt.ie>
Reported-By: Mark Dilger <mark.dilger@enterprisedb.com>
Discussion: https://postgr.es/m/CAHgHdKsn2W=gPBmj7p6MjQFvxB+zZDBkwTSg0o3f5Hh8rkRrsA@mail.gmail.com
Discussion: https://postgr.es/m/CAH2-WzmodSE+gpTd1CRGU9ez8ytyyDS+Kns2r9NzgUp1s56kpw@mail.gmail.com
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions