diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2025-04-04 13:49:00 +0300 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2025-04-04 13:49:00 +0300 |
| commit | 7afca7edef751b8d7c0f5b6402ffcefc11c67fdd (patch) | |
| tree | 9de0e521c2ece32b0087f19360fc6235f0882f9a /src/backend/access/gist/gistbuild.c | |
| parent | 534874fac0b34535c9a5ab9257d6574f78423578 (diff) | |
| download | postgresql-7afca7edef751b8d7c0f5b6402ffcefc11c67fdd.tar.gz postgresql-7afca7edef751b8d7c0f5b6402ffcefc11c67fdd.zip | |
Relax assertion in finding correct GiST parent
Commit 28d3c2ddcf introduced an assertion that if the memorized
downlink location in the insertion stack isn't valid, the parent's
LSN should've changed too. Turns out that was too strict. In
gistFindCorrectParent(), if we walk right, we update the parent's
block number and clear its memorized 'downlinkoffnum'. That triggered
the assertion on next call to gistFindCorrectParent(), if the parent
needed to be split too. Relax the assertion, so that it's OK if
downlinkOffnum is InvalidOffsetNumber.
Backpatch to v13-, all supported versions. The assertion was added in
commit 28d3c2ddcf in v12.
Reported-by: Alexander Lakhin <exclusion@gmail.com>
Reviewed-by: Tender Wang <tndrwang@gmail.com>
Discussion: https://www.postgresql.org/message-id/18396-03cac9beb2f7aac3@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions