On Mon, Dec 23, 2013 at 7:48 AM, <markus.holmb...@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=jxe6v4r7h...@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...@gmail.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
