| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Date: | 2014-01-27 17:58:02 |
| Message-ID: | CA+U5nMJhrdSiop+kHX3WmJdoy6qaKfd=iMB3GUPe54QnJS3-JQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24 January 2014 08:33, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 24 January 2014 07:08, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> On Wed, Jan 15, 2014 at 6:57 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> v15 to fix the above problem.
>>
> v16 attached
v17 attached
This version adds a GUC called ddl_exclusive_locks which allows us to
keep the 9.3 behaviour if we wish it. Some people may be surprised
that their programs don't wait in the same places they used to. We
hope that is a positive and useful behaviour, but it may not always be
so.
I'll commit this on Thurs 30 Jan unless I hear objections.
Thanks
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-01-27 17:58:42 | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Previous Message | Andrew Dunstan | 2014-01-27 17:50:00 | Re: new json funcs |