Re: 9.4 checksum errors in recovery with gin index
| От | Jeff Janes |
|---|---|
| Тема | Re: 9.4 checksum errors in recovery with gin index |
| Дата | |
| Msg-id | CAMkU=1wjro_La2wpowx3x7TjEABFZ9d0S5K-kAk+tfv7FNCxSQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: 9.4 checksum errors in recovery with gin index (Andres Freund <andres@2ndquadrant.com>) |
| Список | pgsql-hackers |
On Wed, May 7, 2014 at 10:34 AM, Andres Freund <andres@2ndquadrant.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@2ndquadrant.com>wrote:> > If you have the WAL a pg_xlogdump grepping for everything referring toHm, try running it with -b specified.
> > that block would be helpful.
> >
>
> The only record which mentions block 28486 by name is this one:
Still nothing more.
If that's the case it seems likely that a PageSetLSN() or PageSetDirty()
> 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.
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
В списке pgsql-hackers по дате отправления: