| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Subject: | Re: Backpatch b61d161c14 |
| Date: | 2020-06-22 12:05:16 |
| Message-ID: | CAA4eK1LD+XXQ17gesFmJrG3LhNbAyAj7PM-aPD+cpk2RJ8YiCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 22, 2020 at 10:35 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2020-06-22 12:11:05 | Re: [POC] Fast COPY FROM command for the table with foreign partitions |
| Previous Message | Amit Kapila | 2020-06-22 12:01:16 | Re: min_safe_lsn column in pg_replication_slots view |