Re: Dumping/restoring fails on inherited generated column

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>

To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Masahiko Sawada <sawada.mshk@gmail.com>, Zhihong Yu <zyu@yugabyte.com>, Masahiko Sawada <masahiko.sawada@2ndquadrant.com>

Date: 2021-05-04T10:27:03Z

Lists: pgsql-hackers

On 26.04.21 14:10, Peter Eisentraut wrote:
> On 05.02.21 15:18, Peter Eisentraut wrote:
>> Anyway, I figured out how to take account of generation expressions 
>> with different column orders.  I used the same approach that we use 
>> for check constraints.  The attached patch is good to go from my 
>> perspective.
> 
> Dusting this off ... this patch should go into the next minor releases. 
> The attached patch is for master but backpatches without manual 
> intervention to PG13 and PG12.

committed

Commits

Fix ALTER TABLE / INHERIT with generated columns
- 13ff139a2384 12.7 landed
- 64190d65f299 13.3 landed
- a970edbed306 14.0 landed
pg_dump: Fix dumping of inherited generated columns
- 1dd6baf78802 12.6 landed
- 1d3ce0223c6a 13.2 landed
- 0bf83648a52d 14.0 landed
Disallow ALTER TABLE ONLY / DROP EXPRESSION
- 539775981746 13.1 landed
- bf797a8d9768 14.0 landed
Fix several DDL issues of generated columns versus inheritance
- 086ffddf3656 13.0 cited