Re: BUG #5703: Streaming replication: FATAL: bad buffer id: 0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Evgeniy" <efreet(at)efreet(dot)ru>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5703: Streaming replication: FATAL: bad buffer id: 0
Date: 2010-10-11 16:34:31
Message-ID: 25449.1286814871@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Evgeniy" <efreet(at)efreet(dot)ru> writes:
> Standby server dies after some minutes with FATAL message:

> 2010-10-11 19:12:17.129 MSD [13864/0]: [5-1] user=,db= LOG: consistent
> recovery state reached at E/A5DCD3A8
> 2010-10-11 19:12:17.139 MSD [13864/0]: [6-1] user=,db= FATAL: bad buffer
> id: 0
> 2010-10-11 19:12:17.139 MSD [13864/0]: [7-1] user=,db= CONTEXT: xlog redo
> Delete list pages (16), node: 1663/18241/93940 blkno: 21207

Hmm ... that seems to be a GIN index message ... and a bit of looking at
the GIN code says that its xlog replay logic is many bricks shy of a
load. I think SR is exposing a pre-existing problem here.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Igor 2010-10-11 20:24:00 BUG #5704: not correct restrictions plperlu
Previous Message Evgeniy 2010-10-11 15:50:36 BUG #5703: Streaming replication: FATAL: bad buffer id: 0