From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Subject: Dumping/restoring fails on inherited generated column
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15829.1575468847.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 04 Dec 2019 09:14:07 -0500
Message-ID: <15830.1575468847@sss.pgh.pa.us>
Precedence: bulk

Run the regression tests with "make installcheck", then:

$ pg_dump -Fc regression >r.dump
$ createdb r2
$ pg_restore -d r2 r.dump
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 6005; 2604 24821 DEFAULT gtest1_1 b postgres
pg_restore: error: could not execute query: ERROR:  column "b" of relation=
 "gtest1_1" is a generated column
Command was: ALTER TABLE ONLY public.gtest1_1 ALTER COLUMN b SET DEFAULT (=
a * 2);


pg_restore: warning: errors ignored on restore: 1
$ =


It looks like gtest1_1 inherits column "b" from gtest1, so possibly
pg_dump is just confused about the combination of inheritance and
generated columns.

I see this in v12 as well as HEAD.  One interesting question is how come
the pg_upgrade test isn't failing --- maybe binary-upgrade mode handles
this case differently?

			regards, tom lane