Re: freeing bms explicitly - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: freeing bms explicitly
Date
Msg-id CAA4eK1JxX-Y3rnLUgPWscJyONSs5KqBnZQHzO_+V48tAty46SQ@mail.gmail.com
Whole thread Raw
In response to Re: freeing bms explicitly  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Thu, Mar 24, 2022 at 7:43 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Mar 23, 2022 at 9:30 AM Zhihong Yu <zyu@yugabyte.com> wrote:
> >
> > On Tue, Mar 22, 2022 at 8:45 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >>
> >> On Tue, Mar 22, 2022 at 3:39 AM Zhihong Yu <zyu@yugabyte.com> wrote:
> >>
> >> Your patch looks good to me. I have found one more similar instance in
> >> the same file and changed that as well accordingly. Let me know what
> >> you think of the attached?
> >>
> >
> > Hi, Amit:
> > The patch looks good to me.
> >
>
> Thanks. I'll push this tomorrow unless Tom or someone else wants to
> look at it or would like to commit.
>

Pushed.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: make MaxBackends available in _PG_init
Next
From: Bharath Rupireddy
Date:
Subject: Re: pg_walinspect - a new extension to get raw WAL data and WAL stats