Re: Logical Replication upgrade - Mailing list pgsql-docs

From vignesh C
Subject Re: Logical Replication upgrade
Date
Msg-id CALDaNm1VOrMXHHPxPmaaBvLN43L2=E5d=KLLUSdiMn8SOfj1VQ@mail.gmail.com
Whole thread
In response to Re: Logical Replication upgrade  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-docs
On Fri, 17 Apr 2026 at 09:25, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Thu, Apr 16, 2026 at 11:16 AM David G. Johnston
> <david.g.johnston@gmail.com> wrote:
> >
> > On Wednesday, April 15, 2026, Amit Kapila <amit.kapila16@gmail.com> wrote:
> >>
> >>
> >> So, how about: "All slots on the old cluster must be usable, i.e.,
> >> their pg_replication_slots.conflicting is false."?
> >
> >
> > That works.
> >
> > Then we’d also change:
> >
> > The new cluster must not have permanent logical slots, i.e., there must be no slots where
pg_replication_slots.temporaryis false. 
> >
> > To be:
> >
> > “The new cluster is only permitted to have temporary logical slots, i.e., ones where pg_replication_slots.temporary
istrue.” 
> >
>
> What you wrote is correct but it is better to keep what is not allowed
> for this case. Based on that, how about the following:
> "The new cluster must not have any permanent logical slots; i.e., any
> existing logical slots must have pg_replication_slots.temporary set to
> true."

Your version seems better, the attached v2 version patch has the
changes for the same.

Regards,
Vignesh

Attachment

pgsql-docs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Logical Replication upgrade
Next
From: Yushu Chen
Date:
Subject: Re: Example. Foreign Keys Constraints. Wrong Columns