Re: Backpatch b61d161c14 - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Backpatch b61d161c14
Date
Msg-id CAA4eK1LD+XXQ17gesFmJrG3LhNbAyAj7PM-aPD+cpk2RJ8YiCA@mail.gmail.com
Whole thread Raw
In response to Backpatch b61d161c14  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Mon, Jun 22, 2020 at 10:35 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> I propose to backpatch b61d161c14 [1] (Introduce vacuum errcontext to
> display additional information.).  In the recent past, we have seen an
> error report similar to "ERROR: found xmin 2157740646 from before
> relfrozenxid 1197" from multiple EDB customers.  A similar report is
> seen on pgsql-bugs as well [2] which I think has triggered the
> implementation of this feature for v13.  Such reports mostly indicate
> database corruption rather than any postgres bug which is also
> indicated by the error-code (from before relfrozenxid) for this
> message.
>

Sorry, the error-code I want to refer to in above sentence was
ERRCODE_DATA_CORRUPTED.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: min_safe_lsn column in pg_replication_slots view
Next
From: Ashutosh Bapat
Date:
Subject: Re: [POC] Fast COPY FROM command for the table with foreign partitions