From: Victor Sudakov <vas@sibptus.ru>
To: Nikhil Shetty <nikhil.dba04@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Lost replication slots after pg_upgrade.
Date: Tue, 8 Feb 2022 03:34:28 +0000
Message-ID: <YgHkxM8Ocn4F3zWi@admin.sibptus.ru> (raw)
In-Reply-To: <CAFpL5Vx__E4hfvvoCQOmGEtAygowJzto_=sQHUTNbXOpUo1PUQ@mail.gmail.com>
References: <CAFpL5Vws1tJnO8_CeOBO6e2q5K4Zbe4==redhV1yLSekm1U4TQ@mail.gmail.com>
<Yftm6IwtRKg5QB7P@admin.sibptus.ru>
<CAFpL5Vx__E4hfvvoCQOmGEtAygowJzto_=sQHUTNbXOpUo1PUQ@mail.gmail.com>
Nikhil Shetty wrote:
>
> Thank you for the update. Is there a way we can retain the physical slot
> during and after upgrade?
What exactly are you trying to achieve?
A minor upgrade does not destroy your slots, actually it does not
modify $PGDATA.
A major upgrade requires creating your replicas from scratch with
pg_basebackup (unless you are adventurous enough to go the rsync way).
pg_basebackup can create the slots for you automagically (-C -S) if
they are gone.
--
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: vas@sibptus.ru, nikhil.dba04@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Lost replication slots after pg_upgrade.
In-Reply-To: <YgHkxM8Ocn4F3zWi@admin.sibptus.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox