Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated. - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated.
Date
Msg-id CAA4eK1L30MiOSPjuDE8QVY4Nce_NRO6_3_-cFUegzByqoqes2g@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated.  (Ashutosh Sharma <ashu.coek88@gmail.com>)
List pgsql-hackers
On Tue, Nov 8, 2016 at 4:23 PM, Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
> Hi,
>
>> I had also thought about it while preparing patch, but I couldn't find
>> any clear use case.  I think it could be useful during development of
>> a module, but not sure if it is worth to add a target.  I think there
>> is no harm in adding such a target, but lets take an opinion from
>> committer or others as well before adding this target.  What do you
>> say?
>
> Ok. We can do that.
>
> I have verified the updated v2 patch. The patch looks good to me. I am
> marking it  as ready for committer.

Thanks for the review.



-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Jeevan Chalke
Date:
Subject: Re: PassDownLimitBound for ForeignScan/CustomScan [take-2]
Next
From: Michael Banck
Date:
Subject: Re: [PATCH] Reload SSL certificates on SIGHUP