| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow some recovery parameters to be changed with reload |
| Date: | 2019-02-07 07:52:34 |
| Message-ID: | d15bc358-f516-0b7b-c301-03cb6cd43a78@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/02/2019 04:35, Michael Paquier wrote:
> On Mon, Feb 04, 2019 at 11:58:28AM +0100, Peter Eisentraut wrote:
>> I think the recovery parameters
>>
>> archive_cleanup_command
>
> Only triggered by the checkpointer.
>
>> promote_trigger_file
>> recovery_end_command
>> recovery_min_apply_delay
>
> Only looked at by the startup process.
>
>> can be changed from PGC_POSTMASTER to PGC_SIGHUP without any further
>> complications (unlike for example primary_conninfo, which is being
>> discussed elsewhere).
>
> I agree that this subset is straight-forward and safe to switch. The
> documentation changes look right.
Committed, thanks.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-02-07 08:14:34 | more unconstify use |
| Previous Message | Michael Paquier | 2019-02-07 06:51:46 | Re: Connection slots reserved for replication |