Re: Lost replication slots after pg_upgrade.

From: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
To: Victor Sudakov <vas(at)sibptus(dot)ru>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>, Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com>
Subject: Re: Lost replication slots after pg_upgrade.
Date: 2022-02-03 06:24:07
Message-ID: CAM+6J9774aZNoS=1=wKMcJZX0hEhQ0mL9BoO37qiDoAGi1dfcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Feb 3, 2022, 10:54 AM Victor Sudakov <vas(at)sibptus(dot)ru> wrote:

> 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
>

A small demo of 11 to 13 upgrade using pg_upgrade and rsync.
It might not be all the best practices, but just following the doc on my
laptop.

>
https://gist.github.com/cabecada/4517af13245383b888833cfc69d741be

Just ensure the backed up configs are in back in and also create the
replication slot.

>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Victor Sudakov 2022-02-03 07:26:47 Re: Lost replication slots after pg_upgrade.
Previous Message Victor Sudakov 2022-02-03 05:23:52 Re: Lost replication slots after pg_upgrade.