Re: FATAL: index contains unexpected zero page at block - Mailing list pgsql-general

From Sergey Konoplev
Subject Re: FATAL: index contains unexpected zero page at block
Date
Msg-id CAL_0b1uzzEXZx+31BFBRGAC1=aBAM0vefagQEL7x8QD97oFSzQ@mail.gmail.com
Whole thread Raw
In response to FATAL: index contains unexpected zero page at block  (markus.holmberg@codento.com)
List pgsql-general
On Mon, Dec 23, 2013 at 7:48 AM,  <markus.holmberg@codento.com> wrote:
>   WARNING:  page 1 of relation base/37706/11821 is uninitialized
>   CONTEXT:  xlog redo vacuum: rel 1663/37706/11821; blk 2, lastBlockVacuumed
> 0
>   PANIC:  WAL contains references to invalid pages
>   CONTEXT:  xlog redo vacuum: rel 1663/37706/11821; blk 2, lastBlockVacuumed
> 0
>
> What could cause "index contains unexpected zero page at block 0" errors as
> shown above on a hot standby?

I think it might be related to the issue [1]. It looks like I managed
to fix it by upgrading to the last minor version (that contains some
critical bug fixes [2] [3]) and by performing reindex after it.

[1] http://www.postgresql.org/message-id/flat/CAL_0b1s4QCkFy_55kk_8XWcJPs7wsgVWf8vn4=jXe6V4R7Hxmg@mail.gmail.com
[2] http://www.databasesoup.com/2013/12/why-you-need-to-apply-todays-update.html
[3] http://www.postgresql.org/docs/current/static/release-9-3-2.html

--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray.ru@gmail.com


pgsql-general by date:

Previous
From: Joseph Kregloh
Date:
Subject: Re: pg_upgrade & tablespaces
Next
From: Steve Crawford
Date:
Subject: postgresql-common breaks logrotate