Re: pg_restore - generated column - not populating
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Santosh Udupi <email@hitha.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-general@lists.postgresql.org
Date: 2021-02-24T00:42:23Z
Lists: pgsql-bugs, pgsql-general
On 2/23/21 4:25 PM, Santosh Udupi wrote: > Yes, this is what we have been doing now:- Backup using pg_dump, create > the new database at the destination, manually create the tables which > give problems, and then do the pg_restore. Another solution for us is to Well that introduces another error, where the restore trips on the existing table(s). By the way this is the first time you mentioned multiple tables. Do they share similar structure? In any case you should not have to do this and in the spirit of identifying the problem and fixing it, what happens if you do: 1) Dump locally 2) Restore locally, without creating the tables ahead. 3) Examine and report back here the table(s) schema(and sample data) after the fresh restore. 4) Drop the table(s) and create from script and populate. Report on whether they work. > backup using pg_dump that comes with pgAdmin (Windows), rsync it to the > destination server and then do the pg_restore on the server. > -- Adrian Klaver adrian.klaver@aklaver.com
Commits
-
pg_dump: Fix dump of generated columns in partitions
- bdaa0d2d7269 12.7 landed
- a6a3a274abd1 13.3 landed
- feb270d1005f 14.0 landed