From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Standby accepts recovery_target_timeline setting? |
Date: | 2019-09-27 14:36:49 |
Message-ID: | 5cd11f19-8fd6-61ee-b9eb-26c43be10eaa@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-09-26 23:02, David Steele wrote:
> On 9/26/19 4:48 PM, Peter Eisentraut wrote:
>> On 2019-09-25 22:21, David Steele wrote:
>>> While testing against PG12 I noticed the documentation states that
>>> recovery targets are not valid when standby.signal is present.
>>>
>>> But surely the exception is recovery_target_timeline? My testing
>>> confirms that this works just as in prior versions with standy_mode=on.
>>
>> Or maybe we should move recovery_target_timeline to a different section?
>> But which one?
>
> Not sure. I think just noting it as an exception is OK, if it is the
> only exception. But currently that does not seem to be the case.
>
>> I don't know if recovery_target_timeline is actually useful to change in
>> standby mode.
OK, I have committed your original documentation patch.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-09-27 14:53:48 | Re: Improving on MAX_CONVERSION_GROWTH |
Previous Message | Robert Haas | 2019-09-27 14:35:47 | Re: abort-time portal cleanup |