Re: pg_dump insert column GENERATED
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Дмитрий Иванов <firstdismay@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Date: 2021-11-21T17:25:54Z
Lists: pgsql-general
On 11/21/21 07:23, Дмитрий Иванов wrote: > Yes and yes. > I don't get regular results in my experiments. I filled in some of the > tables this morning, but now I can't do it again. > > INSERT INTO bpd.plan_calendar (create in version 12) > > OK > I can't do it again. You are going need to provide more information about the above: 1) Define regular results. 2) The query used. 3) The outcome vs what you expected. > Are the below from the bpd.sql file? > Yes > Why does pg_dump insert data into the calculated columns? It shouldn't that is the point of this discussion, why it is happening in your case? So far we have not been able to replicate this behavior on our end, hence the many questions as to your set up. > I entered the data manually via export/import, excluding the problematic > field because its value will be calculated when inserted. > > -- Adrian Klaver adrian.klaver@aklaver.com
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