public inbox for [email protected]help / color / mirror / Atom feed
Replication and Switchover 4+ messages / 3 participants [nested] [flat]
* Replication and Switchover @ 2025-06-06 14:45 Sam Stearns <[email protected]> 0 siblings, 2 replies; 4+ messages in thread From: Sam Stearns @ 2025-06-06 14:45 UTC (permalink / raw) To: Pgsql-admin <[email protected]>; +Cc: Peter Garza <[email protected]>; Henry Ashu <[email protected]> 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 -- Samuel Stearns Team Lead - Database c: 971 762 6879 | o: 971 762 6879 | DAT.com <https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link; ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Replication and Switchover @ 2025-06-06 15:09 Christoph Berg <[email protected]> parent: Sam Stearns <[email protected]> 1 sibling, 1 reply; 4+ messages in thread From: Christoph Berg @ 2025-06-06 15:09 UTC (permalink / raw) To: Sam Stearns <[email protected]>; +Cc: Pgsql-admin <[email protected]>; Peter Garza <[email protected]>; Henry Ashu <[email protected]> Re: Sam Stearns > 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? Create a second database cluster, and move one of the databases into that cluster. "Move" is either dump-restore, or a full restore of the old cluster and dropping the other database. Christoph ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Replication and Switchover @ 2025-06-06 15:17 Sam Stearns <[email protected]> parent: Christoph Berg <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Sam Stearns @ 2025-06-06 15:17 UTC (permalink / raw) To: Christoph Berg <[email protected]>; +Cc: Pgsql-admin <[email protected]>; Peter Garza <[email protected]>; Henry Ashu <[email protected]> Ah. Got it. Makes sense. Thanks, Christoph! Sam On Fri, Jun 6, 2025 at 8:09 AM Christoph Berg <[email protected]> wrote: > Re: Sam Stearns > 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? > Create a > ZjQcmQRYFpfptBannerStart > This Message Is From an Untrusted Sender > You have not previously corresponded with this sender. > > ZjQcmQRYFpfptBannerEnd > > Re: Sam Stearns > > 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? > > Create a second database cluster, and move one of the databases into > that cluster. > > "Move" is either dump-restore, or a full restore of the old cluster > and dropping the other database. > > Christoph > > -- Samuel Stearns Team Lead - Database c: 971 762 6879 | o: 971 762 6879 | DAT.com <https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link; ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Replication and Switchover @ 2025-06-30 18:31 vrms <[email protected]> parent: Sam Stearns <[email protected]> 1 sibling, 0 replies; 4+ messages in thread From: vrms @ 2025-06-30 18:31 UTC (permalink / raw) To: [email protected] 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 ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-06-30 18:31 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-06-06 14:45 Replication and Switchover Sam Stearns <[email protected]> 2025-06-06 15:09 ` Christoph Berg <[email protected]> 2025-06-06 15:17 ` Sam Stearns <[email protected]> 2025-06-30 18:31 ` vrms <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox