Re: Streaming replication bug in 9.3.2, "WAL contains references to invalid pages"
От | Omar Kilani |
---|---|
Тема | Re: Streaming replication bug in 9.3.2, "WAL contains references to invalid pages" |
Дата | |
Msg-id | CA+8F9hgxkzdQ4Hni-+FWPYUGT8q2q9au01MK3_=DVQ+m2Md5_Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Streaming replication bug in 9.3.2, "WAL contains references to invalid pages" (Sergey Konoplev <gray.ru@gmail.com>) |
Список | pgsql-hackers |
We had the same issues running 9.2.4: [2013-10-15 00:23:01 GMT/0/15396] WARNING: page 8789807 of relation base/16429/2349631976 is uninitialized [2013-10-15 00:23:01 GMT/0/15396] CONTEXT: xlog redo vacuum: rel 1663/16429/2349631976; blk 8858544, lastBlockVacuumed 0 [2013-10-15 00:23:01 GMT/0/15396] PANIC: WAL contains references to invalid pages [2013-10-15 00:23:01 GMT/0/15396] CONTEXT: xlog redo vacuum: rel 1663/16429/2349631976; blk 8858544, lastBlockVacuumed 0 [2013-10-15 00:23:11 GMT/0/15393] LOG: startup process (PID 15396) was terminated by signal 6: Aborted [2013-10-15 00:23:11 GMT/0/15393] LOG: terminating any other active server processes Also on an index. I ended up manually patching the heap files at that block location to "fix" the problem. It happened again about 2 weeks after that, then never again. It hit all connected secondaries. On Fri, Jan 3, 2014 at 12:50 PM, Sergey Konoplev <gray.ru@gmail.com> wrote: > On Thu, Jan 2, 2014 at 11:59 AM, Christophe Pettus <xof@thebuild.com> wrote: >> In both cases, the indicated relation was a primary key index. In one case, rebuilding the primary key index caused theproblem to go away permanently (to date). In the second case, the problem returned even after a full dump / restore ofthe master database (that is, after a dump / restore of the master, and reimaging the secondary, the problem returned atthe same primary key index, although of course with a different OID value). >> >> It looks like this has been experienced on 9.2.6, as well: >> >> http://www.postgresql.org/message-id/flat/CAL_0b1s4QCkFy_55kk_8XWcJPs7wsgVWf8vn4=jXe6V4R7Hxmg@mail.gmail.com > > This problem worries me a lot too. If someone is interested I still > have a file system copy of the buggy cluster including WAL. > > -- > 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 > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: