pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Robert Haas <rhaas@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: amcheck: In verify_heapam, allows tuples with xmin 0.
Date: Tue, 28 Mar 2023 20:26:36 +0000
Message-ID: <E1phFtq-000Cdt-QJ@gemulon.postgresql.org> (raw)

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(-)



view thread (3+ messages)  latest in thread

Message-ID: <E1phFtq-000Cdt-QJ@gemulon.postgresql.org>
Permalink:  ../E1phFtq-000Cdt-QJ@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1phFtq-000Cdt-QJ@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: rhaas@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: amcheck: In verify_heapam, allows tuples with xmin 0.
  In-Reply-To: <E1phFtq-000Cdt-QJ@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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