| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: ALTER TABLE lock downgrades have broken pg_upgrade |
| Date: | 2016-05-03 17:44:57 |
| Message-ID: | 20160503174457.p6exbeehmfmgml3w@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-05-03 17:45:16 | Re: what to revert |
| Previous Message | Alvaro Herrera | 2016-05-03 17:41:31 | Re: ALTER TABLE lock downgrades have broken pg_upgrade |