Re: pg_upgrade failing for 200+ million Large Objects
От
Laurenz Albe
Тема
Re: pg_upgrade failing for 200+ million Large Objects
Дата
Msg-id
a71f1582102a9fafcdf98094b8a221c5438e0b42.camel@cybertec.at
Ответ на
Re: pg_upgrade failing for 200+ million Large Objects (Michael Banck)
Список
Дерево обсуждения
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>
On Wed, 2024-03-27 at 10:20 +0100, Michael Banck wrote: > Also, is there a chance this is going to be back-patched? I guess it > would be enough if the ugprade target is v17 so it is less of a concern, > but it would be nice if people with millions of large objects are not > stuck until they are ready to ugprade to v17. It is a quite invasive patch, and it adds new features (pg_restore in bigger transaction patches), so I think this is not for backpatching, desirable as it may seem from the usability angle. Yours, Laurenz Albe
В списке pgsql-hackers по дате отправления
От: Bertrand Drouvot
Дата: