Re: tablecmds.c and lock hierarchy - Mailing list pgsql-hackers

From Robert Haas
Subject Re: tablecmds.c and lock hierarchy
Date
Msg-id CA+Tgmoa_CA19uE9+cKXUs3P=9xr=7eyP-LHT1oHpB6PM7jMWSA@mail.gmail.com
Whole thread Raw
In response to Re: tablecmds.c and lock hierarchy  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: tablecmds.c and lock hierarchy  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Tue, Aug 4, 2015 at 2:41 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Yep, true as things stand now. But this would get broken if we add a
> new lock level between ShareRowExclusiveLock and AccessExclusiveLock
> that does not respect the current monotone hierarchy between those.

But we're probably not going to do that, so it doesn't matter; and if
we do do it, we can worry about it then.  I don't think this is worth
getting concerned about now.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: upgrade failure from 9.5 to head
Next
From: Tom Lane
Date:
Subject: Re: upgrade failure from 9.5 to head