Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Sri Mrudula Attili <sri(at)ebi(dot)ac(dot)uk>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
Date: 2023-11-27 18:58:13
Message-ID: cfaf55a139f7ba48af94b3bc3d39ff6ac9698389.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On Mon, 2023-11-27 at 11:50 +0000, Sri Mrudula Attili wrote:
> ERROR:  could not access status of transaction 16087052
> DETAIL:  Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
> STATEMENT:  SELECT distinct 

That's data corruption.
Time to restore your backup.

Investigate how you got there. Did you run "pg_resetwal"?
Did you restore a database from a file system backup?
Did you remove a "backup_label" file? Is your hardware broken?

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2023-11-27 19:23:37 Re: BUG #17893: Assert failed in heap_update()/_delete() when FK modiified by RI trigger in non-read-committed xact
Previous Message Tom Lane 2023-11-27 17:42:16 Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN

Browse pgsql-general by date

  From Date Subject
Next Message Atul Kumar 2023-11-27 20:11:43 Re: IPV6 issue
Previous Message Christophe Pettus 2023-11-27 18:21:08 Re: Ways to aggregate table info from variable number of schemas