Re: pg_restore - generated column - not populating

Right. pg_dump under the pgAdmin runtime folder works perfectly.  pg_dump
in postgres13 (ubuntu) does not work. Exact same syntax.

When I try to restore, the backup that was taken using pgAdmin's version
restores properly but the one taken using postgres13's pg_dump, restores
the database but does not populate the generated columns. Strange!!

On Tue, Feb 23, 2021 at 7:50 AM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:

> 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
>