Re: pg_upgrade and generated column - Mailing list pgsql-admin

From David G. Johnston
Subject Re: pg_upgrade and generated column
Date
Msg-id CAKFQuwYf-eHb5XVQQ6XcPgQF2Sc0WsVGmnfWvhrHQns+nbV3KA@mail.gmail.com
Whole thread Raw
In response to pg_upgrade and generated column  (kaido vaikla <kaido.vaikla@gmail.com>)
List pgsql-admin
On Monday, March 3, 2025, kaido vaikla <kaido.vaikla@gmail.com> wrote:


...
pg_restore: from TOC entry 226; 1259 17061 TABLE m_access_cert_campaign iamappadmin
pg_restore: error: could not execute query: ERROR:  column "objecttype" in child table must not be a generated column
Command was:
-- For binary upgrade, must preserve pg_type oid
SELECT pg_catalog.binary_upgrade_set_next_pg_type_oid('17063'::pg_catalog.oid);
...


I can find some descriptions of the problems from internet,
but there are no instructions or recommendations on postgres.org,  
what is the "correct" way to upgrade a db if it has a "generated column".
Some suggestion pls. Can i use pg_upgrade at all?

The release notes indicate that the parent and child must agree on whether a column is generated or not.  To upgrade to v16 you must ensure your tartitioned table follows the new rule in v15 first.

David J. 

pgsql-admin by date:

Previous
From: Imran Khan
Date:
Subject: Re: pg_upgrade and generated column
Next
From: Michael Banck
Date:
Subject: Re: Super user password explicit in patroni yml