From: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated. |
Date: | 2016-11-08 10:53:06 |
Message-ID: | CAE9k0Pk1G0Ax+Zvnsye3F4rpR6KYK3ruYq-PEK1k3hV0UL3sLg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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.
With Regards,
Ashutosh Sharma
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2016-11-08 12:23:42 | Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated. |
Previous Message | Amit Kapila | 2016-11-08 04:55:11 | Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated. |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-11-08 11:20:53 | Re: Improving executor performance |
Previous Message | Fabien COELHO | 2016-11-08 10:33:36 | Re: pgbench - allow backslash continuations in \set expressions |