Re: pg_dump insert column GENERATED
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Дмитрий Иванов <firstdismay@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>,
pgsql-general <pgsql-general@lists.postgresql.org>
Date: 2021-11-21T16:24:09Z
Lists: pgsql-general
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay@gmail.com> writes: >> So did you do an ALTER TABLE ... GENERATED ALWAYS AS on bpg.object in >> the Postgres 12 version of the database? > I think you're right, I added later. Hmm, that's suggestive, but I tried making a table that way and still did not see any pg_dump misbehavior. It might be useful to see the results of this query on the v12 server: select attname, attgenerated from pg_attribute where attrelid = 'bpd.object'::regclass and attnum > 0; We should see attgenerated = 's' for the generated column, but maybe we don't? regards, tom lane
Commits
-
Fix pg_dump --inserts mode for generated columns with dropped columns.
- aedc4600d84d 14.2 landed
- 6fc8b145e743 13.6 landed
- 1e7f588ad625 12.10 landed
- 0b126c6a4b00 15.0 landed