| From: | Keith <keith(at)keithf4(dot)com> |
|---|---|
| To: | maria(dot)rossi(at)jackson(dot)com |
| Cc: | pgsql-sql(at)lists(dot)postgresql(dot)org, pgsql-novice(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_dumpall and restore |
| Date: | 2018-10-09 17:58:17 |
| Message-ID: | CAHw75vv6ODFZBTN-n+jBVUfGGv_VYxhxN3p3FTV5fNhdtr9E0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice pgsql-sql |
On Tue, Oct 9, 2018 at 1:19 PM Rossi, Maria <maria(dot)rossi(at)jackson(dot)com> wrote:
> 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
>
>
>
>
>
>
>
Did you use the pg_dumpall binary from 10.5 to create the dump?
Keith
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rossi, Maria | 2018-10-09 18:05:51 | RE: pg_dumpall and restore |
| Previous Message | Rossi, Maria | 2018-10-09 17:18:37 | pg_dumpall and restore |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rossi, Maria | 2018-10-09 18:05:51 | RE: pg_dumpall and restore |
| Previous Message | Rossi, Maria | 2018-10-09 17:18:37 | pg_dumpall and restore |