Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g9vej-0000x6-K3 for pgsql-sql@arkaria.postgresql.org; Tue, 09 Oct 2018 17:18:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g9veh-0001J0-Un for pgsql-sql@arkaria.postgresql.org; Tue, 09 Oct 2018 17:18:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g9veh-0001Io-LP; Tue, 09 Oct 2018 17:18:47 +0000 Received: from dc01pesav001.jacksonnational.com ([12.34.36.219]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g9vec-0007yN-KG; Tue, 09 Oct 2018 17:18:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=jackson.com; i=@jackson.com; q=dns/txt; s=Internal; t=1539105522; x=1570641522; h=from:to:cc:subject:date:message-id:mime-version; bh=Wg9x6zGgc9I+ampGlyLZXJohVKNieF9sVpeSq9Fnd2w=; b=tOp3Bor01mAaXTzZGZKocqRQe68y5WyU54KHHnGJUbOM4zGSG9NuglIg 3+TDWU1b8fSF2BJjejqaK4KsIX4iKt5ebQbIPyDGOQz5uXuASqGUU8E/c SXbySqlmY47NzfNM1acUAQv7RckmQFG9SQgsiqAez6tRe6Fcx+urilAOm E=; X-IronPort-AV: E=Sophos;i="5.54,361,1534824000"; d="scan'208,217";a="28647867" Received: from dc0xpdlpv002.jacksonnational.com (HELO DC03PXMBP003.jacksonnational.com) ([10.5.49.47]) by DC01PESAV001.jacksonnational.com with ESMTP; 09 Oct 2018 13:18:37 -0400 Received: from DC03PXMBP003.jacksonnational.com (10.12.105.32) by DC03PXMBP003.jacksonnational.com (10.12.105.32) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 9 Oct 2018 13:18:37 -0400 Received: from DC03PXMBP003.jacksonnational.com ([10.12.105.32]) by DC03PXMBP003.jacksonnational.com ([10.12.105.32]) with mapi id 15.00.1367.000; Tue, 9 Oct 2018 13:18:37 -0400 From: "Rossi, Maria" To: "'pgsql-sql@lists.postgresql.org'" , "'pgsql-novice@lists.postgresql.org'" CC: "Rossi, Maria" Subject: pg_dumpall and restore Thread-Topic: pg_dumpall and restore Thread-Index: AdRf82EKpgBRUa2CQrS18+mj5Fx3JA== Date: Tue, 9 Oct 2018 17:18:37 +0000 Message-ID: <323742d3468543f590fc081c7fba0c7a@DC03PXMBP003.jacksonnational.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.12.16.10] x-tm-as-product-ver: SMEX-12.5.0.1300-8.5.1010-24146.001 x-tm-as-result: No-18.427900-5.000000-10 x-tmase-matchedrid: d3Skr+z4xAFKDZlLBSf8q/0peXGEEBlvmHAp2UJ8+TxXG3yI9k2vbCWe OHilL0WHP5mpBtPr/e4BZOsOGHKpoUjlo2JU8qCxmHJeAYKlcpNxtWYlDuRQpY9osn8JrdJP2fD FGIaTVjOh/9Db0raJ+12/J3quhJk9n0UoIZ374hfbH8WaUL9qjPxeH3fk9hIOl32P5ZifvYZNAl UAf+JAs1aqCdZD3bg8cvo8LcKILsJVlU1PWtrBs2O43qcJKa+vRvyVHewb0kKCRU18ZWhrYzwQA 5P3VI4Ka4Rtz1l0kwRZo3MLgN1I0PEnzi0PuMx/ngIgpj8eDcBbCjvvWZW+SYGPZcQEXn13H2TD zR13hu5w54ObM/furpOnKzHdKl4Zt3NIuyceZfTVyfwZTcyx4lHvD+xa2Ovy x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No x-tmase-result: 10--18.427900-5.000000 x-tmase-version: SMEX-12.5.0.1300-8.5.1010-24146.001 Content-Type: multipart/alternative; boundary="_000_323742d3468543f590fc081c7fba0c7aDC03PXMBP003jacksonnati_" MIME-Version: 1.0 X-CFilter-Loop: Reflected List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_323742d3468543f590fc081c7fba0c7aDC03PXMBP003jacksonnati_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 th= is and how to prevent? Your help would be much appreciated. Thanks. Maria --_000_323742d3468543f590fc081c7fba0c7aDC03PXMBP003jacksonnati_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 duplic= ate rows, such that it was not able to create the primary key.

I checked the old database, it does not have the dup= s.

Has anyone encountered  having dups rows  = loaded?  Any idea  what caused this and how to prevent?

 

Your help would be much appreciated.

 

Thanks.

Maria

 

 

 

--_000_323742d3468543f590fc081c7fba0c7aDC03PXMBP003jacksonnati_--