Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case
Date
Msg-id CA+U5nMJU7vSJktb8=TR_TcSvAEPU4Ek=kG4Dz=Hq1UW19Ag83Q@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-committers
On Tue, Jul 5, 2011 at 2:46 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Mon, Jul 4, 2011 at 6:14 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> On Mon, Jul 4, 2011 at 9:31 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>> Reset ALTER TABLE lock levels to AccessExclusiveLock in all cases.
>>> Locks on inheritance parent remain at lower level, as they were before.
>>> Remove entry from 9.1 release notes.
>>
>> This commit caused pgbuildfarm failures on 15 machines this morning.
>> Later commit fixes this, I forgot that the lock level is specifically
>> mentioned in regression test results.
>
> I believe you need a similar fix in CreateTrigger() and DefineQueryRewrite().

Thanks. Will address.

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

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Move Trigger and TriggerDesc structs out of rel.h into a new rel
Next
From: fxjr@pgfoundry.org (User Fxjr)
Date:
Subject: npgsql - Npgsql2: [#1011044].