Re: replication failure with GIN index

On Fri, Apr 6, 2012 at 2:56 AM, Rural Hunter <ruralhunter(at)gmail(dot)com> wrote:

> I'm trying to set up a standby server. Both the primary and standby servers
> are on latest version 9.1.3 on ubunt server 10.10. So far I tried to init
> the setup 2 times but both failed after the replication running for some
> time. what can I do to fix this? The log on the standby is shown below:
>
> 2012-04-06 02:31:01 CST [(at)] LOG:  restored log file
> "0000000200000E3C000000F1" from archive
> 2012-04-06 02:35:35 CST [(at)] LOG:  restored log file
> "0000000200000E3C000000F2" from archive
> 2012-04-06 02:36:19 CST [(at)] LOG:  restored log file
> "0000000200000E3C000000F3" from archive
> 2012-04-06 02:36:48 CST [(at)] LOG:  restored log file
> "0000000200000E3C000000F4" from archive
> 2012-04-06 02:37:24 CST [(at)] LOG:  restored log file
> "0000000200000E3C000000F5" from archive
> 2012-04-06 02:37:27 CST [(at)] PANIC:  GIN metapage disappeared
> 2012-04-06 02:37:27 CST [(at)] CONTEXT:  xlog redo Update metapage, node:
> 37547844/16405/83896882 blkno: 4294967295
> 2012-04-06 02:37:28 CST [(at)] LOG:  startup process (PID 24912) was terminated
> by signal 6: Aborted
> 2012-04-06 02:37:28 CST [(at)] LOG:  terminating any other active server
> processes

The blkno is all wrong, so it looks like a clear bug to me.

Blkno has been set to -1.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services