Re: pgsql: Raise a warning if there is a possibility of data from multiple

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <akapila(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Raise a warning if there is a possibility of data from multiple
Date: 2022-09-09 01:03:04
Message-ID: CAA4eK1+eBBPfP2-jNNe2WkfhvOUwofxopF8uC4ArNoYimyv9wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Sep 8, 2022 at 7:28 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> > I feel it is better to be consistent across the entire code base
> > unless there is a reason for doing it differently. Does anyone else
> > have any thoughts on this matter?
>
> That sounds like it would be a pretty massive and unnecessary patch.
>

Fair enough. Do you mind being consistent in this regard for logical
replication-related code? BTW, is there a reason we prefer to write in
one or another way (with or without appending schema_name)?

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2022-09-09 01:53:51 pgsql: Replace load of functions by direct calls for some WIN32
Previous Message Michael Paquier 2022-09-09 01:02:07 pgsql: Add more error context to RestoreBlockImage() and consume it