Re: ALTER TABLE lock strength reduction patch is unsafe - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: ALTER TABLE lock strength reduction patch is unsafe
Date
Msg-id CA+U5nMKmWtAyqQS7gxzL9MjwLNXXWjLmFe0jEbgB0FX9F4p9GA@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLE lock strength reduction patch is unsafe  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On 27 January 2014 17:58, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 24 January 2014 08:33, Simon Riggs <simon@2ndquadrant.com> wrote:
>> On 24 January 2014 07:08, Peter Geoghegan <pg@heroku.com> wrote:
>>> On Wed, Jan 15, 2014 at 6:57 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>>> v15 to fix the above problem.
>>>
>> v16 attached
>
> v17 attached

Frostbite...

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe
Next
From: Simon Riggs
Date:
Subject: Re: A better way than tweaking NTUP_PER_BUCKET