Re: Replication and Switchover

From: vrms <vrms(at)netcologne(dot)de>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Replication and Switchover
Date: 2025-06-30 18:31:09
Message-ID: 481ee580-ba4b-445d-bf35-7bee976543b4@netcologne.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Nikhil Shetty 2025-07-01 05:53:55 pg_upgrade failure due to dependencies
Previous Message Achilleas Mantzios 2025-06-30 15:08:52 Re: Fast Logical replication setup, via VM clone , PostgreSQL 16.9