Re: PATCH: standby crashed when replay block which truncated in standby but failed to truncate in master node
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>, Thunder <thunder1@126.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-17T04:47:01Z
Lists: pgsql-hackers
On Thu, Jan 16, 2020 at 11:17:36PM +0900, Fujii Masao wrote: > OK, I updated the patch that way. > Attached is the updated version of the patch. Thanks. I have few tweaks to propose to the docs. + raise a PANIC-level error, aborting the recovery. Setting Instead of "PANIC-level error", I would just use "PANIC error", and instead of "aborting the recovery" just "crashing the server". + causes the system to ignore those WAL records WAL records are not ignored, but errors caused by incorrect page references in those WAL records are. The current phrasing sounds like the WAL records are not applied. Another thing that I just recalled. Do you think that it would be better to mention that invalid page references can only be seen after reaching the consistent point during recovery? The information given looks enough, but I was just wondering if that's worth documenting or not. -- Michael
Commits
-
Add GUC ignore_invalid_pages.
- 41c184bc642b 13.0 landed