pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: amcheck: In verify_heapam, allows tuples with xmin 0.
3+ messages / 1 participants
[nested] [flat]

* pgsql: amcheck: In verify_heapam, allows tuples with xmin 0.
@ 2023-03-28 20:26 Robert Haas <rhaas@postgresql.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Robert Haas @ 2023-03-28 20:26 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b7cea58822c67724effc711ae28e4077a01a7cd6

Modified Files
--------------
contrib/amcheck/verify_heapam.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* pgsql: amcheck: In verify_heapam, allows tuples with xmin 0.
@ 2023-03-28 20:26 Robert Haas <rhaas@postgresql.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Robert Haas @ 2023-03-28 20:26 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/453f53821fa549d3e46c87a076fc7849fab9a948

Modified Files
--------------
contrib/amcheck/verify_heapam.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* pgsql: amcheck: In verify_heapam, allows tuples with xmin 0.
@ 2023-03-28 20:26 Robert Haas <rhaas@postgresql.org>
  0 siblings, 0 replies; 3+ messages in thread

From: Robert Haas @ 2023-03-28 20:26 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/e3363cda9cb615718be14e2780fa4c82f3d270de

Modified Files
--------------
contrib/amcheck/verify_heapam.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2023-03-28 20:26 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-03-28 20:26 pgsql: amcheck: In verify_heapam, allows tuples with xmin 0. Robert Haas <rhaas@postgresql.org>
2023-03-28 20:26 pgsql: amcheck: In verify_heapam, allows tuples with xmin 0. Robert Haas <rhaas@postgresql.org>
2023-03-28 20:26 pgsql: amcheck: In verify_heapam, allows tuples with xmin 0. Robert Haas <rhaas@postgresql.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox