Re: Documentation to upgrade logical replication cluster

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Subject: Re: Documentation to upgrade logical replication cluster
Date: 2024-09-26 10:58:54
Message-ID: CAA4eK1+xvunTRHVjyN7OTg2HwQKbFVRFR9YndazJp-vnCgO8LQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 25, 2024 at 6:07 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> Yes, users can upgrade either the publisher first and then the
> subscriber, or the subscriber first and then the publisher. I felt
> this note is necessary only for the "Steps to upgrade a two-node
> logical replication cluster," as it may confuse users in other types
> of logical replication with questions such as: a) Which subscriber
> should be upgraded first? b) Which subscriptions should be disabled?
> c) When should each subscription be enabled?
> The attached patch includes a note for the same.
>

Pushed.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2024-09-26 11:53:07 RE: long-standing data loss bug in initial sync of logical replication
Previous Message Alexander Korotkov 2024-09-26 10:57:25 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part