| From: | Sri Mrudula Attili <sri(at)ebi(dot)ac(dot)uk> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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-29 17:20:20 |
| Message-ID: | d2abe33c-fb65-492d-9671-2541a349a9db@ebi.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Hello Laurenz,
Thanks for your response.
This error we are seeing on a delphix Virtual database that was
refreshed using the snapshot of production standalone database.
It keeps the database in pg_start_backup and to take the snapshot.
I did check the dsource(production) database logs and it hasnt got any
error like this.
Thanks,
Sri Attili
On 27/11/2023 18:58, Laurenz Albe wrote:
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-11-29 17:29:15 | Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success. |
| Previous Message | Tom Lane | 2023-11-29 16:14:00 | Re: BUG #18217: ALTER TABLE IF EXISTS not being honored with DROP CONSTRAINT IF EXISTS |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-11-29 17:29:15 | Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success. |
| Previous Message | Davin Shearer | 2023-11-29 15:32:54 | Re: Emitting JSON to file using COPY TO |