Re: BUG #17528: ERROR: could not access status of transaction 1997627701 - Mailing list pgsql-bugs

From Andrey Borodin
Subject Re: BUG #17528: ERROR: could not access status of transaction 1997627701
Date
Msg-id F6932542-979B-4607-8AF4-9FDFB0F773CF@yandex-team.ru
Whole thread Raw
In response to BUG #17528: ERROR: could not access status of transaction 1997627701  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs

> On 22 Jun 2022, at 08:34, PG Bug reporting form <noreply@postgresql.org> wrote:
>
> Hello.
> I've found on our server (PostgreSQL 10.19 on x86_64-pc-linux-gnu, compiled
> by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit)
>

It seems you have encountered data corruption. This might be a result of some different causes. Can you please describe
moredetails and history of your installation? 
Do you update your system? Was it running on versions before 10.16? Somewhat related bug was fixed, but AFAIR it was
onlyreproducible only if the system is running near xid wraparound regularly. 
Does your block storage feels OK? Are data_checksums enabled?
Can you check installation with amcheck and heapcheck?
Do you have backups? If so - can you bisect when the corruption first appeared?

You can try to fix a copy of the cluster with tools like pg_surgery or pg_dirty_hands.

Best regards, Andrey Borodin.


pgsql-bugs by date:

Previous
From: Raman Kumar
Date:
Subject: Re: BUG #17524: Increase in WAL size due to logical replication with publication contain a table with low activity.
Next
From: Kevin Wolf
Date:
Subject: Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command