Re: pg_upgrde failed : logical replication : alter_subscription_add_log - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: pg_upgrde failed : logical replication : alter_subscription_add_log
Date
Msg-id CAA4eK1+jyT28a2isiyqNuqaRAneJO=mdvqarCBUUSqUurRcKPg@mail.gmail.com
Whole thread Raw
In response to [MASSMAIL]pg_upgrde failed : logical replication : alter_subscription_add_log  (Perumal Raj <perucinci@gmail.com>)
List pgsql-hackers
Note - Please keep pgsql-hackers in CC while responding.

On Fri, Apr 12, 2024 at 10:44 AM Perumal Raj <perucinci@gmail.com> wrote:
Thanks Amit for the update,


19.6.3. Upgrading Data via Replication

It is also possible to use logical replication methods to create a standby server with the updated version of PostgreSQL. This is possible because logical replication supports replication between different major versions of PostgreSQL. The standby can be on the same computer or a different computer. Once it has synced up with the primary server (running the older version of PostgreSQL), you can switch primaries and make the standby the primary and shut down the older database instance. Such a switch-over results in only several seconds of downtime for an upgrade.

This method of upgrading can be performed using the built-in logical replication facilities as well as using external logical replication systems such as pglogicalSlonyLondiste, and Bucardo.

What is "built-in logical replication" ? 


See docs at [1].

--
With Regards,
Amit Kapila

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Add notes to pg_combinebackup docs
Next
From: Amit Kapila
Date:
Subject: Re: promotion related handling in pg_sync_replication_slots()