Re: Allow some recovery parameters to be changed with reload

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow some recovery parameters to be changed with reload
Date: 2020-08-05 15:41:49
Message-ID: CA+TgmoZ9i4-ob0jE1i_ZV3g-ojCOxcEPYsNZ29fSXYVN+rMpsw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 28, 2020 at 7:21 AM Sergei Kornilov <sk(at)zsrv(dot)org> wrote:
> So...
> We call restore_command only when walreceiver is stopped.
> We use restore_command only in startup process - so we have no race condition between processes.
> We have some issues here? Or we can just make restore_command reloadable as attached?

I don't see the problem here, either. Does anyone else see a problem,
or some reason not to press forward with this?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-08-05 15:49:00 Re: Replace remaining StrNCpy() by strlcpy()
Previous Message Etsuro Fujita 2020-08-05 15:20:50 Re: Yet another issue with step generation in partition pruning