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

From Robert Haas
Subject Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case
Date
Msg-id CA+Tgmob3J+d5NFq+_LJGuteV31Ym63fULMde=pffpg3xaaX6tQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case  (Simon Riggs <simon@2ndQuadrant.com>)
Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
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().

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

pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: pgsql: Fix typo in sslmode documentation
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Move Trigger and TriggerDesc structs out of rel.h into a new rel