| From: | "Rossi, Maria" <maria(dot)rossi(at)jackson(dot)com> |
|---|---|
| To: | "'pgsql-sql(at)lists(dot)postgresql(dot)org'" <pgsql-sql(at)lists(dot)postgresql(dot)org>, "'pgsql-novice(at)lists(dot)postgresql(dot)org'" <pgsql-novice(at)lists(dot)postgresql(dot)org> |
| Cc: | "Rossi, Maria" <maria(dot)rossi(at)jackson(dot)com> |
| Subject: | pg_dumpall and restore |
| Date: | 2018-10-09 17:18:37 |
| Message-ID: | 323742d3468543f590fc081c7fba0c7a@DC03PXMBP003.jacksonnational.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice pgsql-sql |
Hi,
I upgraded our postgres database from V9.3 to V10.5. Used pg_dumpall then restore it to the new instance.
After the restore, we notice that 1 table had duplicate rows, such that it was not able to create the primary key.
I checked the old database, it does not have the dups.
Has anyone encountered having dups rows loaded? Any idea what caused this and how to prevent?
Your help would be much appreciated.
Thanks.
Maria
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith | 2018-10-09 17:58:17 | Re: pg_dumpall and restore |
| Previous Message | Richard Brockie | 2018-09-30 04:12:48 | SSL tunnel configuration help |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith | 2018-10-09 17:58:17 | Re: pg_dumpall and restore |
| Previous Message | Gary Stainburn | 2018-10-09 13:18:01 | left outer join to pull in most recent record |