pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sri Mrudula Attili <sri@ebi.ac.uk>
To: Laurenz Albe <laurenz.albe@cybertec.at>
To: pgsql-general@lists.postgresql.org
Subject: Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
Date: Wed, 29 Nov 2023 17:20:20 +0000
Message-ID: <d2abe33c-fb65-492d-9671-2541a349a9db@ebi.ac.uk> (raw)
In-Reply-To: <cfaf55a139f7ba48af94b3bc3d39ff6ac9698389.camel@cybertec.at>
References: <a0513574-8f17-4ca4-887e-a5c11c1f01b8@ebi.ac.uk>
	<2004615f-02a6-4058-97f2-31f019e1cf93@ebi.ac.uk>
	<cfaf55a139f7ba48af94b3bc3d39ff6ac9698389.camel@cybertec.at>

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





view thread (9+ messages)  latest in thread

Message-ID: <d2abe33c-fb65-492d-9671-2541a349a9db@ebi.ac.uk>
Permalink:  ../d2abe33c-fb65-492d-9671-2541a349a9db@ebi.ac.uk/
Also on:    postgresql.org/message-id/d2abe33c-fb65-492d-9671-2541a349a9db@ebi.ac.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: sri@ebi.ac.uk, laurenz.albe@cybertec.at, pgsql-general@lists.postgresql.org
  Subject: Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
  In-Reply-To: <d2abe33c-fb65-492d-9671-2541a349a9db@ebi.ac.uk>
  References: <a0513574-8f17-4ca4-887e-a5c11c1f01b8@ebi.ac.uk> <2004615f-02a6-4058-97f2-31f019e1cf93@ebi.ac.uk> <cfaf55a139f7ba48af94b3bc3d39ff6ac9698389.camel@cybertec.at> <d2abe33c-fb65-492d-9671-2541a349a9db@ebi.ac.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox