Re: 9.4 checksum errors in recovery with gin index

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 9.4 checksum errors in recovery with gin index
Date: 2014-05-07 20:01:02
Message-ID: CAMkU=1wjro_La2wpowx3x7TjEABFZ9d0S5K-kAk+tfv7FNCxSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 7, 2014 at 10:34 AM, Andres Freund <andres(at)2ndquadrant(dot)com>wrote:

> Hi,
>
> On 2014-05-07 10:21:26 -0700, Jeff Janes wrote:
> > On Wed, May 7, 2014 at 12:48 AM, Andres Freund <andres(at)2ndquadrant(dot)com
> >wrote:
> > > If you have the WAL a pg_xlogdump grepping for everything referring to
> > > that block would be helpful.
> > >
> >
> > The only record which mentions block 28486 by name is this one:
>
> Hm, try running it with -b specified.
>

Still nothing more.

>
> > rmgr: Gin len (rec/tot): 1576/ 1608, tx: 77882205, lsn:
> > 11/30F4C2C0, prev 11/30F4C290, bkp: 0000, desc: Insert new list page,
> node:
> > 1663/16384/16396 blkno: 28486
> >
> > However, I think that that record precedes the recovery start point.
>
> If that's the case it seems likely that a PageSetLSN() or PageSetDirty()
> are missing somewhere...
>

Wouldn't that result in corrupted data after crash recovery when checksum
failures are ignored? I haven't seen any of that.

Cheers,

Jeff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-05-07 20:13:33 Re: Wanted: jsonb on-disk representation documentation
Previous Message Tom Lane 2014-05-07 19:52:50 Re: Wanted: jsonb on-disk representation documentation