Postgres Pro
Downloads
Home   >   mailing lists

Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node
Date
Msg-id 20191003045750.GG1586@paquier.xyz
Whole thread Raw
In response to Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node
List pgsql-hackers
Tree view 
On Thu, Oct 03, 2019 at 01:49:34PM +0900, Fujii Masao wrote:
> But this can cause subsequent recovery to always fail with invalid-pages error
> and the server not to start up. This is bad. So, to allviate the situation,
> I'm thinking it would be worth adding something like igore_invalid_pages
> developer parameter. When this parameter is set to true, the startup process
> always ignores invalid-pages errors. Thought?

That could be helpful.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: PATCH: standby crashed when replay block which truncated instandby but failed to truncate in master node
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench - allow to create partitioned tables