Re: pg_upgrade failing for 200+ million Large Objects - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: pg_upgrade failing for 200+ million Large Objects
Date
Msg-id a71f1582102a9fafcdf98094b8a221c5438e0b42.camel@cybertec.at
Whole thread Raw
In response to Re: pg_upgrade failing for 200+ million Large Objects  (Michael Banck <mbanck@gmx.net>)
Responses Re: pg_upgrade failing for 200+ million Large Objects
List pgsql-hackers
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 by date:

Previous
From: David Rowley
Date:
Subject: Re: Properly pathify the union planner
Next
From: Bertrand Drouvot
Date:
Subject: Re: Introduce XID age and inactive timeout based replication slot invalidation