| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Santosh Udupi <email(at)hitha(dot)net> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_restore - generated column - not populating |
| Date: | 2021-02-23 15:26:57 |
| Message-ID: | 89a62c70-4386-a3ef-f2ea-5e0f448cef11@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
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 | Santosh Udupi | 2021-02-23 15:39:15 | Re: pg_restore - generated column - not populating |
| Previous Message | Tom Lane | 2021-02-23 15:12:13 | Re: BUG #16888: Reoccurring group by clauses makes system slower |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-23 15:28:55 | Re: New operators and class for jsonb with gin indexing |
| Previous Message | Tom Lane | 2021-02-23 15:24:20 | Re: Custom base type and suboptimal query plans |