Re: extra semicolon in postgres_fdw test cases

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: extra semicolon in postgres_fdw test cases
Date: 2021-03-31 05:57:46
Message-ID: CAA4eK1+GTsc5U4q6zAKVBi37RsjYjNrt7OY6iqw+fFY9b5Mskg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 31, 2021 at 9:47 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Wed, Mar 31, 2021 at 9:35 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> >
> > On Tue, Mar 30, 2021 at 05:00:53PM +0530, Amit Kapila wrote:
> > > Looks good to me as well but I think one can choose not to backpatch
> > > as there is no functional impact but OTOH, there is some value in
> > > keeping tests/code consistent.
> >
> > FWIW, I would not bother with the back branches for just that, but if
> > you feel that this is better, of course feel free.
> >
>
> Fair enough. I'll push this just for HEAD.
>

Pushed!

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message torikoshia 2021-03-31 06:02:02 Re: Get memory contexts of an arbitrary backend process
Previous Message Kyotaro Horiguchi 2021-03-31 05:36:24 Re: Stronger safeguard for archive recovery not to miss data