Re: Hot standby 9.2.6 -> 9.2.6 PANIC: WAL contains references to invalid pages
От | Sergey Konoplev |
---|---|
Тема | Re: Hot standby 9.2.6 -> 9.2.6 PANIC: WAL contains references to invalid pages |
Дата | |
Msg-id | CAL_0b1tXw6cwFQv7LaU743sA+KjGvHKnOhjhfvLn-3YGLJ1x1Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Hot standby 9.2.6 -> 9.2.6 PANIC: WAL contains references to invalid pages (Sergey Konoplev <gray.ru@gmail.com>) |
Список | pgsql-bugs |
On Thu, Dec 19, 2013 at 2:37 PM, Sergey Konoplev <gray.ru@gmail.com> wrote: > Yesterday I upgraded both master and replica servers to 9.2.6, > performed SET vacuum_freeze_table_age = 0; VACUUM; and then rebuild > the replica from scratch. > > 2013-12-19 20:51:22 MSK 19938 @ from [vxid:1/0 txid:0] [] WARNING: > page 14833 of relation base/16436/3321003988 is uninitialized > 2013-12-19 20:51:22 MSK 19938 @ from [vxid:1/0 txid:0] [] CONTEXT: > xlog redo vacuum: rel 1663/16436/3321003988; blk 38538, > lastBlockVacuumed 0 > 2013-12-19 20:51:22 MSK 19938 @ from [vxid:1/0 txid:0] [] PANIC: WAL > contains references to invalid pages > 2013-12-19 20:51:22 MSK 19938 @ from [vxid:1/0 txid:0] [] CONTEXT: > xlog redo vacuum: rel 1663/16436/3321003988; blk 38538, > lastBlockVacuumed 0 FYI Today we noticed that the PANIC happens on the same relation with the same block and page. This is an index, created on Dec 10 with its daily partition that was before I upgraded Postgres from 9.2.4 to 9.2.6. So probably it was a kind of aftermath of the pre-9.2.6 problems. I have done reindex of this particular index on production, but I still have the buggy copy of the cluster in case if someone would like to dig the problem deeper. Will keep you informed. -- 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-bugs по дате отправления: