From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Perumal Raj <perucinci(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_upgrde failed : logical replication : alter_subscription_add_log |
Date: | 2024-04-12 10:25:57 |
Message-ID: | CAA4eK1+jyT28a2isiyqNuqaRAneJO=mdvqarCBUUSqUurRcKPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Note - Please keep pgsql-hackers in CC while responding.
On Fri, Apr 12, 2024 at 10:44 AM Perumal Raj <perucinci(at)gmail(dot)com> wrote:
> Thanks Amit for the update,
>
> Documentation says : https://www.postgresql.org/docs/15/upgrading.html
>
> 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 pglogical, Slony, Londiste, and Bucardo.
>
> What is "built-in logical replication" ?
>
See docs at [1].
[1] - https://www.postgresql.org/docs/devel/logical-replication.html
--
With Regards,
Amit Kapila
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2024-04-12 10:37:06 | Re: promotion related handling in pg_sync_replication_slots() |
Previous Message | David Steele | 2024-04-12 09:50:59 | Re: Add notes to pg_combinebackup docs |