public inbox for [email protected]  

help / color / mirror / Atom feed

From: vrms <[email protected]>
To: [email protected]
Subject: Re: Replication and Switchover
Date: Mon, 30 Jun 2025 20:31:09 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAN6TVj=01f6At2L4X7WM8g1c+18up8mSLB1GSKzJdJNAEUtaag@mail.gmail.com>
References: <CAN6TVj=01f6At2L4X7WM8g1c+18up8mSLB1GSKzJdJNAEUtaag@mail.gmail.com>

just to remind myself about the 'switchover' process ... in such a case 
as the on at hand here there is no ambition to actually switch and 
replicate back to the original main, but rather use replication 
mechanics the 'clone' the cluster (or in your case part of it), right?

In order to 'untie' the cloned cluster you would

   1. stop the replica
   2. remove the standby.signal file from the replicas $PGDATA
   3. delete the postgresql.auto.conf  on the replica
   4. start the replica anew

... is that a fair assumption? Or is the above more or less what "SELECT 
pg_promote() ;" does?

I guess #3 might not even be a hard requirement as it is being ignored 
in absence of a standby.signal




On 06.06.25 16:45, Sam Stearns wrote:
> Howdy,
>
> We have 2 databases running out of a single database cluster.  We 
> would like to set up replication from the existing host to a new host 
> and then switchover to that new host.  One of the databases is ready 
> to switchover now while the other database is going to take a bit more 
> time to be ready for the switchover.
>
> We would like to switchover the database that is ready now so we can 
> start performing load testing against it.  Is it possible to 
> switchover one database in a cluster while not switching over the other?
>
> Thanks,
>
> Sam

reply

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Replication and Switchover
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox