Re: Btree index left link changed unexpectedly after bringing up 8.3.11 warm standby

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Btree index left link changed unexpectedly after bringing up 8.3.11 warm standby
Date: 2010-10-28 15:32:48
Message-ID: 1288279867-sup-3998@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Excerpts from Mark Kirkwood's message of jue oct 28 02:20:56 -0300 2010:
> I'm seeing this on a Pitrtools managed warm standby box that we
> periodically bring the db fully up on in order to test if the standby is
> good.
>
> After the standby is up, then a db wide VACUUM produces:
>
> 2010-10-28 17:20:51 NZDT WARNING: relation "node" page 248500 is
> uninitialized --- fixing
> 2010-10-28 17:20:51 NZDT WARNING: relation "node" page 248502 is
> uninitialized --- fixing
> 2010-10-28 17:20:51 NZDT WARNING: relation "node" page 248504 is
> uninitialized --- fixing
> 2010-10-28 17:20:54 NZDT ERROR: left link changed unexpectedly in block
> 21042 of index "content_node_node_type_id_inserted_idx"
>
> I'm guessing the index error is due to the uninitialized table pages
> (the index "content_node_node_type_id_inserted_idx" is on the "node"
> table).

Not necessarily ... You still have the index in that state, right?
We could try some diagnostics on it.

> Are the uninitialized pages cause for concern, or merely an artifact
> of log shipping?

These *should* be innocuous.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexia Lau 2010-10-28 16:13:34 Re: BUG
Previous Message Dharmendra Goyal 2010-10-28 08:34:12 Re: BUG