On Mon, Jul 4, 2011 at 6:14 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Mon, Jul 4, 2011 at 9:31 AM, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

• Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case at 2011-07-04 10:14:59 from Simon Riggs

Responses

• Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case at 2011-07-05 15:00:25 from Simon Riggs
• Re: pgsql: Reset ALTER TABLE lock levels to AccessExclusiveLock in all case at 2011-07-07 17:17:27 from Tom Lane

pgsql-committers by date

Next:	From: Tom Lane	Date: 2011-07-05 14:47:03
	Subject: Re: pgsql: Move Trigger and TriggerDesc structs out of rel.h into a new rel
Previous:	From: Magnus Hagander	Date: 2011-07-05 07:48:11
	Subject: pgsql: Fix typo in sslmode documentation