Re: Time-Delayed Standbys

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Time-Delayed Standbys
Date: 2013-12-12 08:45:01
Message-ID: CA+U5nM+V8e-zJC=k=6hODFRkARBm9o_0DpTTkDP1p7y1mAe__w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12 December 2013 08:19, KONDO Mitsumasa
<kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> (2013/12/12 7:23), Fabrízio de Royes Mello wrote:
>>
>> On Wed, Dec 11, 2013 at 7:47 PM, Andres Freund <andres(at)2ndquadrant(dot)com
>> > * hot_standby=off: Makes delay useable with wal_level=archive (and thus
>> > a lower WAL volume)
>> > * standby_mode=off: Configurations that use tools like pg_standby and
>> > similar simply don't need standby_mode=on. If you want to trigger
>> > failover from within the restore_command you *cannot* set it.
>> > * recovery_target_*: It can still make sense if you use
>> > pause_at_recovery_target.
>
>
> I don't think part of his arguments are right very much... We can just set
> stanby_mode=on when we use "min_standby_apply_delay" with pg_standby and
> similar simply tools. However, I tend to agree with not to need to prohibit
> except for standby_mode. So I'd like to propose that changing parameter name
> of "min_standby_apply_delay" to "min_recovery_apply_delay". It is natural
> for this feature.

OK

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2013-12-12 09:09:21 Re: Time-Delayed Standbys
Previous Message KONDO Mitsumasa 2013-12-12 08:19:21 Re: Time-Delayed Standbys