Simon Riggs <si...@2ndquadrant.com> writes:
> On 3 May 2016 at 18:07, Tom Lane <t...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
