aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2023-03-28 16:16:53 -0400
committerRobert Haas <rhaas@postgresql.org>2023-03-28 16:17:03 -0400
commit453f53821fa549d3e46c87a076fc7849fab9a948 (patch)
tree1f0a6bc573e07d7afe950447f519be53fe259614 /src/backend/access/gist/gistbuild.c
parentbf5c4b3d9da67ab0dd8a5a560804f88370c42866 (diff)
downloadpostgresql-453f53821fa549d3e46c87a076fc7849fab9a948.tar.gz
postgresql-453f53821fa549d3e46c87a076fc7849fab9a948.zip
amcheck: In verify_heapam, allows tuples with xmin 0.
Commit e88754a1965c0f40a723e6e46d670cacda9e19bd caused that case to be reported as corruption, but Peter Geoghegan pointed out that it can legitimately happen in the case of a speculative insertion that aborts, so we'd better not flag it as corruption after all. Back-patch to v14, like the commit that introduced the issue. Discussion: http://postgr.es/m/CAH2-WzmEabzcPTxSY-NXKH6Qt3FkAPYHGQSe2PtvGgj17ZQkCw@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions