Re: Switching XLog source from archive to streaming when primary available

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>

To: nathandbossart@gmail.com

Cc: bharath.rupireddyforpostgres@gmail.com, cary.huang@highgo.ca, pgsql-hackers@lists.postgresql.org, satyanarlapuram@gmail.com

Date: 2022-09-09T05:26:57Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add basic TAP tests for the low-level backup method, take two
- 071e3ad59d6f 17.0 cited
Add a failover option to subscriptions.
- 776621a5e479 17.0 cited
Make all Perl warnings fatal
- c5385929593d 17.0 cited
Add PostgreSQL::Test::Cluster::advance_wal
- c161ab74f76a 17.0 cited
Rename wal_keep_segments to wal_keep_size.
- c3fe108c025e 14.0 cited

At Thu, 8 Sep 2022 10:53:56 -0700, Nathan Bossart <nathandbossart@gmail.com> wrote in 
> On Thu, Sep 08, 2022 at 05:16:53PM +0530, Bharath Rupireddy wrote:
> > I'm attaching the v3 patch with the review comments addressed, please
> > review it further.
> 
> My general point is that we should probably offer some basic preventative
> measure against flipping back and forth between streaming and archive
> recovery while making zero progress.  As I noted, maybe that's as simple as
> having WaitForWALToBecomeAvailable() attempt to restore a file from archive
> at least once before the new parameter forces us to switch to streaming
> replication.  There might be other ways to handle this.

+1.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center