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: pgsql-general@lists.postgresql.org
Date: 2021-02-23T15:50:48Z
Lists: pgsql-bugs, pgsql-general
On 2/23/21 7:39 AM, Santosh Udupi wrote: > Got it. Must be the version difference. I run pgAdmin on Windows PC but > direct pg_dump on Ubuntu 20.04. The OS does not really make a difference it is the pg_dump/restore versions and the Postgres server(s) versions that are important. > > On Tue, Feb 23, 2021 at 7:27 AM Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 2/23/21 6:36 AM, Santosh Udupi wrote: > > The pg_restore command is actually pg_restore -Ft -d mydb > mydb.tar (my > > mistake). > > > > I didn't provide the -h -p -U since I use the super user account to > > restore (I will try adding them). The restore had always worked > until I > > altered the table in the source database. > > > > After I added the column, the restore still takes place but does not > > populate the generated column. I did a backup using pgAdmin and the > > restore populated all data using the same syntax on the tar file. > So my > > suspicion is that pg_dump is not doing the dump correctly. I will > work > > on it further. Thanks for your suggestions. > > > > pgAdmin uses pg_dump to do backups. > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > -- 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