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

From Andres Freund
Subject Re: ALTER TABLE lock downgrades have broken pg_upgrade
Date
Msg-id 20160503174457.p6exbeehmfmgml3w@alap3.anarazel.de
Whole thread Raw
In response to ALTER TABLE lock downgrades have broken pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Stephen Frost <sfrost@snowman.net>)
Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

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.

- Andres



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: ALTER TABLE lock downgrades have broken pg_upgrade
Next
From: Andres Freund
Date:
Subject: Re: what to revert