Re: pg_upgrade failing for 200+ million Large Objects
От
Tom Lane
Тема
Re: pg_upgrade failing for 200+ million Large Objects
Дата
Msg-id
227228.1616259220@sss.pgh.pa.us
Ответ на
Re: pg_upgrade failing for 200+ million Large Objects (Bruce Momjian)
Список
Дерево обсуждения
Re: pg_upgrade failing for 200+ million Large Objects Jan Wieck <jan@wi3ck.info>
Re: pg_upgrade failing for 200+ million Large Objects Nathan Bossart <nathandbossart@gmail.com>
Re: pg_upgrade failing for 200+ million Large Objects Jacob Champion <jchampion@timescale.com>
Re: pg_upgrade failing for 200+ million Large Objects Nathan Bossart <nathandbossart@gmail.com>
Re: pg_upgrade failing for 200+ million Large Objects Jacob Champion <jchampion@timescale.com>
Re: pg_upgrade failing for 200+ million Large Objects "Kumar, Sachin" <ssetiya@amazon.com>
Re: pg_upgrade failing for 200+ million Large Objects Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_upgrade failing for 200+ million Large Objects "Kumar, Sachin" <ssetiya@amazon.com>
Re: pg_upgrade failing for 200+ million Large Objects Andres Freund <andres@anarazel.de>
Re: pg_upgrade failing for 200+ million Large Objects "Kumar, Sachin" <ssetiya@amazon.com>
Re: pg_upgrade failing for 200+ million Large Objects Nathan Bossart <nathandbossart@gmail.com>
Re: pg_upgrade failing for 200+ million Large Objects Michael Paquier <michael@paquier.xyz>
Bruce Momjian writes: > On Sat, Mar 20, 2021 at 11:23:19AM -0400, Tom Lane wrote: >> Of course, that just reduces the memory consumption on the client >> side; it does nothing for the locks. Can we get away with releasing the >> lock immediately after doing an ALTER OWNER or GRANT/REVOKE on a blob? > Well, in pg_upgrade mode you can, since there are no other cluster > users, but you might be asking for general pg_dump usage. Yeah, this problem doesn't only affect pg_upgrade scenarios, so it'd really be better to find a way that isn't dependent on binary-upgrade mode. regards, tom lane
В списке pgsql-hackers по дате отправления