agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Rossi, Maria <maria.rossi@jackson.com>
Cc: 'pgsql-sql@lists.postgresql.org' <pgsql-sql@lists.postgresql.org>
Cc: 'pgsql-novice@lists.postgresql.org' <pgsql-novice@lists.postgresql.org>
Subject: Re: pg_dumpall and restore
Date: Tue, 09 Oct 2018 14:32:02 -0400
Message-ID: <19950.1539109922@sss.pgh.pa.us> (raw)
In-Reply-To: <47175ca8aea768568fb51e1a91c94d436ef79d97.camel@cybertec.at>
References: <323742d3468543f590fc081c7fba0c7a@DC03PXMBP003.jacksonnational.com>
<47175ca8aea768568fb51e1a91c94d436ef79d97.camel@cybertec.at>
Laurenz Albe <laurenz.albe@cybertec.at> writes:
> Rossi, Maria wrote:
>> Has anyone encountered having dups rows loaded? Any idea what caused this and how to prevent?
> I don't believe that pg_dumpall miraculously duplicated the row.
What seems much more likely is that the dump script was loaded twice.
The script expects to be fed into an empty database ...
regards, tom lane
view thread (8+ messages) latest in thread
Message-ID: <19950.1539109922@sss.pgh.pa.us>
Permalink: ../19950.1539109922@sss.pgh.pa.us/
Also on: postgresql.org/message-id/19950.1539109922@sss.pgh.pa.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, laurenz.albe@cybertec.at, maria.rossi@jackson.com, pgsql-sql@lists.postgresql.org, pgsql-novice@lists.postgresql.org
Subject: Re: pg_dumpall and restore
In-Reply-To: <19950.1539109922@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox