WAL replay issue from 9.6.8 to 9.6.10

2018-08-28 Thread Dave Peticolas
Hello, I'm seeing some issues with WAL replay on a test server running 9.6.10 using WAL archived from a 9.6.8 primary server. It reliably PANICs during replay with messages like so: WARNING: page 1209270272 of relation base/16422/47496599 does not exist CONTEXT: xlog redo at 4810/C84F8A0 for Btr

Re: WAL replay issue from 9.6.8 to 9.6.10

2018-08-28 Thread Dave Peticolas
On Tue, Aug 28, 2018 at 9:21 PM Andreas Kretschmer wrote: > On 29 August 2018 06:02:45 CEST, Dave Peticolas wrote: > >Hello, I'm seeing some issues with WAL replay on a test server running > >9.6.10 using WAL archived from a 9.6.8 primary server. It reliably > > &

Re: WAL replay issue from 9.6.8 to 9.6.10

2018-08-29 Thread Dave Peticolas
On Wed, Aug 29, 2018 at 4:54 AM Michael Paquier wrote: > On Wed, Aug 29, 2018 at 08:31:50AM +0200, Alexander Kukushkin wrote: > > 2018-08-29 6:02 GMT+02:00 Dave Peticolas : > >> Hello, I'm seeing some issues with WAL replay on a test server running > >> 9.6.10

Re: WAL replay issue from 9.6.8 to 9.6.10

2018-08-29 Thread Dave Peticolas
On Wed, Aug 29, 2018 at 1:50 PM Michael Paquier wrote: > On Wed, Aug 29, 2018 at 09:15:29AM -0700, Dave Peticolas wrote: > > Oh, perhaps I do, depending on what you mean by worker. There are a > couple > > of periodic processes that connect to the server to obtain metrics. Is

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

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

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 > <mailto:adrian.kla...@aklaver.com>> wrote: > > > > On 08/31/2018 08:02 AM, Dave Peticolas wrote: >

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 >> >

error in vacuum

2018-09-01 Thread Dave Peticolas
I'm seeing this error on a table repeatedly: found update xid 3433096759 <(343)%20309-6759> from before relfrozenxid 3498422955 What can I do to repair this table? thanks, dave

Re: error in vacuum

2018-09-01 Thread Dave Peticolas
On Sat, Sep 1, 2018 at 4:47 PM Dave Peticolas wrote: > I'm seeing this error on a table repeatedly: > > found update xid 3433096759 <(343)%20309-6759> from before relfrozenxid > 3498422955 > > What can I do to repair this table? > > This is version 9.6.

Re: error in vacuum

2018-09-01 Thread Dave Peticolas
On Sat, Sep 1, 2018, 5:10 PM Adrian Klaver wrote: > On 09/01/2018 04:47 PM, Dave Peticolas wrote: > > I'm seeing this error on a table repeatedly: > > > > found update xid 3433096759 from before > > relfrozenxid 3498422955 > > Where is this, your primary or

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 corr

Re: error in vacuum

2018-09-01 Thread Dave Peticolas
On Sat, Sep 1, 2018 at 5:28 PM Dave Peticolas wrote: > On Sat, Sep 1, 2018, 5:10 PM Adrian Klaver > wrote: > >> On 09/01/2018 04:47 PM, Dave Peticolas wrote: >> > I'm seeing this error on a table repeatedly: >> > >> > found update xi

Re: error in vacuum

2018-09-01 Thread Dave Peticolas
On Sat, Sep 1, 2018 at 6:56 PM Tom Lane wrote: > Dave Peticolas writes: > >>> I'm seeing this error on a table repeatedly: > >>> found update xid 3433096759 <(343)%20309-6759> from before > relfrozenxid 3498422955 > > >> This is a primar

Re: error in vacuum

2018-09-01 Thread Dave Peticolas
On Sat, Sep 1, 2018 at 7:24 PM Andres Freund wrote: > On 2018-09-01 19:02:18 -0700, Dave Peticolas wrote: > > On Sat, Sep 1, 2018 at 6:56 PM Tom Lane wrote: > > > > > Dave Peticolas writes: > > > >>> I'm seeing this error on a table repeated

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: > > > > > > &