Re: Time-Delayed Standbys

From: KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp>
To: fabriziomello(at)gmail(dot)com, Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Simon Riggs <simon(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:19:21
Message-ID: 52A97189.2040009@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(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.

Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2013-12-12 08:45:01 Re: Time-Delayed Standbys
Previous Message Pavel Stehule 2013-12-12 07:42:44 Re: In-Memory Columnar Store