From: | Victor Sudakov <vas(at)sibptus(dot)ru> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Cc: | Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com> |
Subject: | Re: Lost replication slots after pg_upgrade. |
Date: | 2022-02-03 05:23:52 |
Message-ID: | Yftm6IwtRKg5QB7P@admin.sibptus.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Nikhil Shetty wrote:
> Hi,
> I have a Primary and Standby running on Postgres v11.7.
>
> I was following the document to upgrade a PG v11.7 cluster to PG v13.4.
> After upgrade using pg_upgrade on primary, I ran rsync to setup standby
> PG13 but when I started the primary, the replication slots were not
> present. How will standby start streaming in this case?
>
> We are using physical replication slots.
You can create the replication slots manually with
pg_create_physical_replication_slot() any time.
However, unless you are very brave and know what you are doing, I'd
recommend using pg_basebackup to setup a standby, not rsync. You can
even use the -C and -S options of pg_basebackup to create the slots
for you, and many other pg_basebackup's nice options.
--
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49(at)fidonet
From | Date | Subject | |
---|---|---|---|
Next Message | Vijaykumar Jain | 2022-02-03 06:24:07 | Re: Lost replication slots after pg_upgrade. |
Previous Message | Nikhil Shetty | 2022-02-02 10:17:58 | Lost replication slots after pg_upgrade. |