From: Rui DeSousa <rui@crazybean.net>
To: Tim <timfosho@gmail.com>
Cc: posgres support <pgsql-admin@postgresql.org>
Subject: Re: Cascading Replication - Standby Recovering Faster from Archive rather than Upstream node
Date: Thu, 9 Feb 2023 13:47:48 -0500
Message-ID: <B88AE058-0049-40CB-AF4B-C807279127B0@crazybean.net> (raw)
In-Reply-To: <CAKhLO5ju66vc=rWCJ7uwqmfiGP4YZa_0Sk5H8ZGLWmxC_QiELQ@mail.gmail.com>
References: <CAKhLO5ju66vc=rWCJ7uwqmfiGP4YZa_0Sk5H8ZGLWmxC_QiELQ@mail.gmail.com>
> On Feb 9, 2023, at 1:41 PM, Tim <timfosho@gmail.com> wrote:
>
> Is there anything I can do to force to WAL stream instead of recovering from the archive without removing the restore_command setting?
Yes, you can use a replication slot to ensure that the WAL file is available on the primary until the DR node consumes it. You have to make sure you have enough WAL free space to accommodate any lag or disruption issues.=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rui@crazybean.net, timfosho@gmail.com
Subject: Re: Cascading Replication - Standby Recovering Faster from Archive rather than Upstream node
In-Reply-To: <B88AE058-0049-40CB-AF4B-C807279127B0@crazybean.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox