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

From Stephen Frost
Subject Re: ALTER TABLE lock downgrades have broken pg_upgrade
Date
Msg-id 20160503174946.GQ10850@tamriel.snowman.net
Whole thread Raw
In response to Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
* Andres Freund (andres@anarazel.de) wrote:
> On 2016-05-03 12:07:51 -0400, Tom Lane wrote:
> > I think possibly the easiest fix for this is to have pg_upgrade,
> > instead of RESETting a nonexistent option, RESET something that's
> > still considered to require AccessExclusiveLock.  "user_catalog_table"
> > would work, looks like; though I'd want to annotate its entry in
> > reloptions.c to warn people away from downgrading its lock level.
>
> Alternatively we could just add a function for adding a toast table -
> that seems less hacky and less likely to be broken in the future.

+1

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER TABLE lock downgrades have broken pg_upgrade
Next
From: Andres Freund
Date:
Subject: Re: ALTER TABLE lock downgrades have broken pg_upgrade