Re: Diagnostic comment in LogicalIncreaseXminForSlot - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Diagnostic comment in LogicalIncreaseXminForSlot
Date
Msg-id CAA4eK1JwZL8eP-5SNswBGXAo6Ne0RD1t6QoXsnxzm1nnW3Rdzw@mail.gmail.com
Whole thread Raw
In response to Re: Diagnostic comment in LogicalIncreaseXminForSlot  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Fri, Oct 1, 2021 at 6:36 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> On Fri, Oct 1, 2021 at 1:45 AM Jaime Casanova
> <jcasanov@systemguards.com.ec> wrote:
> >
> > On Tue, Sep 07, 2021 at 11:14:23AM +0530, Amit Kapila wrote:
> > > On Mon, Sep 6, 2021 at 5:29 PM Ashutosh Bapat
> > > <ashutosh.bapat@enterprisedb.com> wrote:
> > > >
> > > > Yeah, I agree. Sorry for missing that.
> > > >
> > > > The updated patch looks good to me.
> > > >
> > >
> > > Pushed!
> > >
> >
> > This patch is still on "Needs review"!
> > Should we change it to Committed or is expected something else
> > about it?
>
> Yes, the patch already gets committed (4c347885). So I also think we
> should mark it as Committed.
>

Right, I have changed the status to Committed.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: minor gripe about lax reloptions parsing for views
Next
From: Ashutosh Sharma
Date:
Subject: Re: non-superusers are allowed to drop the replication user, but are not allowed to alter or even create them, is that ok?