Re: pg_upgrade failures with large partition definitions on upgrades from ~13 to 14~

2023-02-08 Thread Michael Paquier
On Thu, Feb 09, 2023 at 12:33:06AM -0500, Tom Lane wrote: > It might be worth expending a pre-check on, if only because the > check could offer some advice about fixing the problem. Based on the information coming from pg_class, yes, something could be reported back. Now things get more hairy if

Re: pg_upgrade failures with large partition definitions on upgrades from ~13 to 14~

2023-02-08 Thread Tom Lane
Michael Paquier writes: > The following SQL sequence causes a failure of pg_upgrade when these > are executed on a cluster of ~13, doing an upgrade to 14~, assuming > that the relation page size is 8kB. > ... > No fields have been added to pg_class between 13 and 14, however the > amount of data s

pg_upgrade failures with large partition definitions on upgrades from ~13 to 14~

2023-02-08 Thread Michael Paquier
Hi all, The following SQL sequence causes a failure of pg_upgrade when these are executed on a cluster of ~13, doing an upgrade to 14~, assuming that the relation page size is 8kB. This creates a partition table with a set of values large enough that it can be created in ~13: CREATE TABLE parent_