Re: BUG #13822: Slave terminated - WAL contains references to invalid page
От | Michael Paquier |
---|---|
Тема | Re: BUG #13822: Slave terminated - WAL contains references to invalid page |
Дата | |
Msg-id | CAB7nPqSDPVAQoDp+coVHCNh_J+9R9nKTERQBfS3Qz3dK3iM7yg@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #13822: Slave terminated - WAL contains references to invalid page (marek.petr@tieto.com) |
Ответы |
Re: BUG #13822: Slave terminated - WAL contains references to
invalid page
|
Список | pgsql-bugs |
On Thu, Dec 17, 2015 at 9:50 PM, <marek.petr@tieto.com> wrote: > Several days after one in-place and one out of place upgrade from 9.3 to 9.4 > version following event occured on both environments: > > 2015-12-15 22:35:18 CET @ WARNING: page 4119662 of relation base/16422/18134 > is uninitialized > 2015-12-15 22:35:18 CET @ CONTEXT: xlog redo visible: rel 1663/16422/18134; > blk 4119662 > 2015-12-15 22:35:18 CET @ PANIC: WAL contains references to invalid pages > 2015-12-15 22:35:18 CET @ CONTEXT: xlog redo visible: rel 1663/16422/18134; > blk 4119662 > 2015-12-15 22:35:18 CET @ LOG: startup process (PID 22269) was terminated by > signal 6: Aborted > 2015-12-15 22:35:18 CET @ LOG: terminating any other active server process > > Once it was TOAST and another regular table. This is the indication of some data corruption, page 4119662 referring to at least a size of 31GB, but this so less information it is hard to guess what could happen. Is 31GB more or less the size of this relation? If you deploy a slave from a fresh base backup, do you still see the error? That's unlikely so if it is the second time you are seeing this problem, but it may be a problem of corruption within the WAL segments themselves. -- Michael
В списке pgsql-bugs по дате отправления: