Re: About a recently-added message - Mailing list pgsql-hackers

From shveta malik
Subject Re: About a recently-added message
Date
Msg-id CAJpy0uC5UTonWdAYGZf=y=xPrEcG=By+Yqzc155KNebksTA1Mw@mail.gmail.com
Whole thread Raw
In response to Re: About a recently-added message  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: About a recently-added message
List pgsql-hackers
On Thu, Feb 15, 2024 at 8:26 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Feb 14, 2024 at 7:51 PM Euler Taveira <euler@eulerto.com> wrote:
> >
> > On Wed, Feb 14, 2024, at 8:45 AM, Amit Kapila wrote:
> >
> > Now, I am less clear about whether to quote "logical" or not in the
> > above message. Do you have any suggestions?
> >
> >
> > The possible confusion comes from the fact that the sentence contains "must be"
> > in the middle of a comparison expression. For pg_createsubscriber, we are using
> >
> >         publisher requires wal_level >= logical
> >
> > I suggest to use something like
> >
> >         slot synchronization requires wal_level >= logical
> >
>
> This sounds like a better idea but shouldn't we directly use this in
> 'errmsg' instead of a separate 'errhint'? Also, if change this, then
> we should make a similar change for other messages in the same
> function.

+1 on changing the msg(s) suggested way. Please find the patch for the
same. It also removes double quotes around the variable names

thanks
Shveta

Attachment

pgsql-hackers by date:

Previous
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Synchronizing slots from primary to standby
Next
From: David Benjamin
Date:
Subject: Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions