Re: Standby trying "restore_command" before local WAL - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Standby trying "restore_command" before local WAL
Date
Msg-id CANP8+jKooAqhs7sox5y8vYs0mM-jCBtQR0inmKQpX8oQLFq2fw@mail.gmail.com
Whole thread Raw
In response to Standby trying "restore_command" before local WAL  (Emre Hasegeli <emre@hasegeli.com>)
List pgsql-hackers
On 31 July 2018 at 13:55, Emre Hasegeli <emre@hasegeli.com> wrote:
> Currently the startup process tries the "restore_command" before
> the WAL files locally available under pg_wal/ [1].  I believe we should
> change this behavior.

> If there will be a consensus on fixing this, I can try to prepare
> a patch.  The company, I am currently working for, is also interested
> in sponsoring a support company to fix this problem.

Seems like a new option to choose your preference would help here,
with the default being the existing behavior.

Suggestions for parameter name welcome.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: Adding a note to protocol.sgml regarding CopyData
Next
From: "Daniel Verite"
Date:
Subject: Re: Doc patch: add RECURSIVE to bookindex