Re: ALTER TABLE lock strength reduction patch is unsafe

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, 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 20:25:22
Message-ID: CA+TgmoY_3JXfh7_x7u+DkhE4Hb459XdsUbrMsFdS7YAbZDuY5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 27, 2014 at 12:58 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> 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.

I haven't reviewed the patch, but -1 for adding a GUC.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-01-27 20:35:58 Re: ALTER TABLE lock strength reduction patch is unsafe
Previous Message Peter Geoghegan 2014-01-27 19:55:42 Re: Failure while inserting parent tuple to B-tree is not fun