Re: About a recently-added message

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Euler Taveira <euler(at)eulerto(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: About a recently-added message
Date: 2024-02-15 03:52:23
Message-ID: CAJpy0uC5UTonWdAYGZf=y=xPrEcG=By+Yqzc155KNebksTA1Mw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 15, 2024 at 8:26 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Wed, Feb 14, 2024 at 7:51 PM Euler Taveira <euler(at)eulerto(dot)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 Content-Type Size
v1-0001-Fix-quotation-of-variable-names.patch application/octet-stream 5.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Benjamin 2024-02-15 03:58:17 Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions
Previous Message Zhijie Hou (Fujitsu) 2024-02-15 03:35:34 RE: Synchronizing slots from primary to standby