Horton

Re: Is Recovery actually paused?

Dilip Kumar <dilipbalaut@gmail.com>

View thread View on postgr.es
From: Dilip Kumar <dilipbalaut@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Yugo Nagata <nagata@sraoss.co.jp>, Masahiko Sawada <sawada.mshk@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Simon Riggs <simon@2ndquadrant.com>
Date: 2021-03-01T05:07:55Z
Lists: pgsql-hackers 
On Fri, Feb 26, 2021 at 1:33 PM Kyotaro Horiguchi
<horikyota.ntt@gmail.com> wrote:
>
> At Thu, 25 Feb 2021 13:22:53 +0530, Dilip Kumar <dilipbalaut@gmail.com> wrote in
> > On Thu, Feb 25, 2021 at 12:42 PM Kyotaro Horiguchi
> > <horikyota.ntt@gmail.com> wrote:
> > > The latest version applies (almost) cleanly to the current master and
> > > works fine.
> > > I don't have further comment on this.
> > >
> > > I'll wait for a day before marking this RfC in case anyone have
> > > further comments.
> >
> > Okay.
>
> Hearing nothing, done that.

Thanks.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. Be clear about whether a recovery pause has taken effect.

  2. Pause recovery for insufficient parameter settings

  3. Remove most volatile qualifiers from xlog.c