Hot standby failing with PANIC: WAL contains references to invalid pages

From: TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp>
To: pgsql-general(at)postgresql(dot)org
Subject: Hot standby failing with PANIC: WAL contains references to invalid pages
Date: 2017-12-15 03:20:13
Message-ID: 20171215122013.a63bc0a14c2af13ea513024e@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi folks,

I got the same failure with the following report on Amazon Linux 2017.09
and postgresql95-9.5.8-1.73.amzn1.x86_64.

The WAL's RMGR ID and its type (Heap2/VISIBLE) are also same.
The servers had worked for over 2 weeks and the standby crashed.

Firstly we suspected something low layer curruption, but any exact
reason haven't been found yet.
I think possibility of a bug now because of the other similar report.

Does anyone has any idea or similar experience?

[Hot standby failing with page # of relation # is uninitialized]
https://www.postgresql.org/message-id/a46709a5-3c41-7acb-1db0-60a317283795@tracktrans.com

(log output @stanby)
2017-12-11 18:14:16 JST [5094]: [13-1] db=,user=,state=01000 WARNING: page 1646627 of relation pg_tblspc/16407/PG_9.5_201510051/16406/31164 is uninitialized
2017-12-11 18:14:16 JST [5094]: [14-1] db=,user=,state=01000 CONTEXT: xlog redo Heap2/VISIBLE: cutoff xid 210320
2017-12-11 18:14:16 JST [5094]: [15-1] db=,user=,state=XX000 PANIC: WAL contains references to invalid pages
2017-12-11 18:14:16 JST [5094]: [16-1] db=,user=,state=XX000 CONTEXT: xlog redo Heap2/VISIBLE: cutoff xid 210320
2017-12-11 18:14:16 JST [5088]: [5-1] db=,user=,state=00000 LOG: startup process (PID 5094) was terminated by signal 6: Aborted
2017-12-11 18:14:16 JST [5088]: [6-1] db=,user=,state=00000 LOG: terminating any other active server processes

with best regards,
Haruka Takatsuka

Browse pgsql-general by date

  From Date Subject
Next Message Ben Madin 2017-12-15 04:23:17 Re: Can postgresql ignore DST ?
Previous Message Venkata B Nagothi 2017-12-15 02:20:52 Re: Can postgresql ignore DST ?