Re: A recent message added to pg_upgade - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: A recent message added to pg_upgade
Date
Msg-id CAA4eK1L_=y2UVXDCHcMz-17v1yX2sSOuTmJHDFETVqy_eR=6tw@mail.gmail.com
Whole thread Raw
In response to Re: A recent message added to pg_upgade  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: A recent message added to pg_upgade
List pgsql-hackers
On Fri, Oct 27, 2023 at 8:52 AM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
> On Fri, Oct 27, 2023 at 8:28 AM Kyotaro Horiguchi:
> The above errhint LGTM. How about a slightly different errmsg, like
> the following?
>
> +                    errmsg("cannot invalidate replication slots when
> in binary upgrade mode"),
> +                    errhint("Set \"max_slot_wal_keep_size\" to -1 to
> avoid invalidation."));
>
> ".... when in binary upgrade mode" is being used in many places.
>

By this time slot may be already invalidated, so how about:
"replication slot was invalidated when in binary upgrade mode"?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: maybe a type_sanity. sql bug
Next
From: Peter Smith
Date:
Subject: Re: A recent message added to pg_upgade