RE: pg_dumpall and restore

From: "Rossi, Maria" <maria(dot)rossi(at)jackson(dot)com>
To: Keith <keith(at)keithf4(dot)com>
Cc: "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>
Subject: RE: pg_dumpall and restore
Date: 2018-10-09 18:05:51
Message-ID: 4cb8957e977348fdb7dcae372daf70ed@DC03PXMBP003.jacksonnational.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice pgsql-sql

Yes, I did use the V10.5 pg_dumpall

Maria A Rossi

From: Keith <keith(at)keithf4(dot)com>
Sent: Tuesday, October 9, 2018 1:58 PM
To: Rossi, Maria <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

EXTERNAL EMAIL

On Tue, Oct 9, 2018 at 1:19 PM Rossi, Maria <maria(dot)rossi(at)jackson(dot)com<mailto: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

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Laurenz Albe 2018-10-09 18:28:25 Re: pg_dumpall and restore
Previous Message Keith 2018-10-09 17:58:17 Re: pg_dumpall and restore

Browse pgsql-sql by date

  From Date Subject
Next Message Laurenz Albe 2018-10-09 18:28:25 Re: pg_dumpall and restore
Previous Message Keith 2018-10-09 17:58:17 Re: pg_dumpall and restore