Re: ALTER TABLE lock downgrades have broken pg_upgrade - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ALTER TABLE lock downgrades have broken pg_upgrade
Date
Msg-id 1627.1462632558@sss.pgh.pa.us
Whole thread Raw
In response to Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> On 3 May 2016 at 18:07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Or at least, it did until Simon decided that ALTER TABLE RESET
>> doesn't require AccessExclusiveLock.

> On reflection, this still seems like a good idea.

Yes, what pg_upgrade was doing was clearly a hack, and not a very nice one.

> I accept that it is my bug and should fix it.

It's moot at this point, see 1a2c17f8e.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pg_dump broken for non-super user
Next
From: Tom Lane
Date:
Subject: "pg_xxx" role name restriction not applied to bootstrap superuser?