From: Alexander Pogodin <alex_pogodin@yahoo.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Cascaded Replication question
Date: Mon, 9 Jan 2023 15:24:27 +0000 (UTC)
Message-ID: <1254601719.7524472.1673277867599@mail.yahoo.com> (raw)
References: <1254601719.7524472.1673277867599.ref@mail.yahoo.com>
Hello, guys!
I have a setup with 3 PgSQL instances connected with streaming replication as such:
+---+ +---+ +---+
| A | <-- | B | <-- | C |
+---+ +---+ +---+
When the link to A is broken, I manually promote server B and expect server C to follow new timeline: I have recovery_target_timeline set to latest. But that's not the case. To follow new timeline I have to restart server C. Is it the designed behavior or am I missing something?
I am using the latest 10.x version.
Could you, please, advise?
Best regards, Alex Pogodin.
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: alex_pogodin@yahoo.com, pgsql-admin@lists.postgresql.org
Subject: Re: Cascaded Replication question
In-Reply-To: <1254601719.7524472.1673277867599@mail.yahoo.com>
* 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