Re: locate DB corruption

2018-09-02 Thread Dave Peticolas
On Sun, Sep 2, 2018 at 4:51 AM Stephen Frost wrote: > Greetings, > > * Dave Peticolas (d...@krondo.com) wrote: > > On Sat, Sep 1, 2018 at 5:09 PM Adrian Klaver > > wrote: > > > > > On 09/01/2018 04:45 PM, Dave Peticolas wrote: > > > > > > > Well restoring from a backup of the primary does seem t

Re: locate DB corruption

2018-09-02 Thread Stephen Frost
Greetings, * Dave Peticolas (d...@krondo.com) wrote: > On Sat, Sep 1, 2018 at 5:09 PM Adrian Klaver > wrote: > > > On 09/01/2018 04:45 PM, Dave Peticolas wrote: > > > > > Well restoring from a backup of the primary does seem to have fixed the > > > issue with the corrupt table. > > > > Pretty su

Re: locate DB corruption

2018-09-01 Thread Dave Peticolas
On Sat, Sep 1, 2018 at 5:09 PM Adrian Klaver wrote: > On 09/01/2018 04:45 PM, Dave Peticolas wrote: > > > Well restoring from a backup of the primary does seem to have fixed the > > issue with the corrupt table. > > Pretty sure it was not that the table was corrupt but that transaction > informat

Re: locate DB corruption

2018-09-01 Thread Adrian Klaver
On 09/01/2018 04:45 PM, Dave Peticolas wrote: Well restoring from a backup of the primary does seem to have fixed the issue with the corrupt table. Pretty sure it was not that the table was corrupt but that transaction information was missing from pg_clog. In a previous post you mentioned y

Re: locate DB corruption

2018-09-01 Thread Dave Peticolas
On Fri, Aug 31, 2018 at 8:48 PM Dave Peticolas wrote: > On Fri, Aug 31, 2018 at 5:19 PM Adrian Klaver > wrote: > >> On 08/31/2018 08:51 AM, Dave Peticolas wrote: >> > On Fri, Aug 31, 2018 at 8:14 AM Adrian Klaver < >> adrian.kla...@aklaver.com >> > > wrote: >> >

Re: locate DB corruption

2018-08-31 Thread Dave Peticolas
On Fri, Aug 31, 2018 at 5:19 PM Adrian Klaver wrote: > On 08/31/2018 08:51 AM, Dave Peticolas wrote: > > On Fri, Aug 31, 2018 at 8:14 AM Adrian Klaver > > wrote: > > > > On 08/31/2018 08:02 AM, Dave Peticolas wrote: > > > Hello, I'm running into the fol

Re: locate DB corruption

2018-08-31 Thread Adrian Klaver
On 08/31/2018 08:51 AM, Dave Peticolas wrote: On Fri, Aug 31, 2018 at 8:14 AM Adrian Klaver > wrote: On 08/31/2018 08:02 AM, Dave Peticolas wrote: > Hello, I'm running into the following error running a large query on a > database restored from

Re: locate DB corruption

2018-08-31 Thread Dave Peticolas
On Fri, Aug 31, 2018 at 8:14 AM Adrian Klaver wrote: > On 08/31/2018 08:02 AM, Dave Peticolas wrote: > > Hello, I'm running into the following error running a large query on a > > database restored from WAL replay: > > > > could not access status of transaction 330569126 > > DETAIL: Could not ope

Re: locate DB corruption

2018-08-31 Thread Adrian Klaver
On 08/31/2018 08:02 AM, Dave Peticolas wrote: Hello, I'm running into the following error running a large query on a database restored from WAL replay: could not access status of transaction 330569126 DETAIL: Could not open file "pg_clog/0C68": No such file or directory Postgres version? Wh

locate DB corruption

2018-08-31 Thread Dave Peticolas
Hello, I'm running into the following error running a large query on a database restored from WAL replay: could not access status of transaction 330569126 DETAIL: Could not open file "pg_clog/0C68": No such file or directory Searches of this mailing list seem to indicate this means a database row