From: | Santosh Udupi <email(at)hitha(dot)net> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_restore - generated column - not populating |
Date: | 2021-02-23 15:39:15 |
Message-ID: | CACLRvHaK2tCmXPKSrjKAiQdVV0+zMQ_Gy3onpkFXD4VLnm46Ng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
Got it. Must be the version difference. I run pgAdmin on Windows PC but
direct pg_dump on Ubuntu 20.04.
On Tue, Feb 23, 2021 at 7:27 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2021-02-23 15:50:48 | Re: pg_restore - generated column - not populating |
Previous Message | Adrian Klaver | 2021-02-23 15:26:57 | Re: pg_restore - generated column - not populating |
From | Date | Subject | |
---|---|---|---|
Next Message | Luka Zivkovic | 2021-02-23 15:40:42 | Re: New operators and class for jsonb with gin indexing |
Previous Message | Tom Lane | 2021-02-23 15:28:55 | Re: New operators and class for jsonb with gin indexing |