Horton

Re: Dumping/restoring fails on inherited generated column

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, andrewbille@gmail.com, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-10-02T17:07:04Z
Lists: pgsql-hackers 
On 2020-09-29 18:37, Tom Lane wrote:
> Unfortunately this has still got a problem: it will mishandle the case of
> a child column that is GENERATED while its parent is not.  Peter opined
> way upthread that we should not allow that, but according to my testing
> we do.

Did I opine that?  Commit 086ffddf3656fb3d24d9a73ce36cb1102e42cc90 
explicitly allowed that case.  What we don't want is the other way around.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Fix ALTER TABLE / INHERIT with generated columns

  2. pg_dump: Fix dumping of inherited generated columns

  3. Disallow ALTER TABLE ONLY / DROP EXPRESSION

  4. Fix several DDL issues of generated columns versus inheritance