public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: flik <[email protected]>
Cc: [email protected]
Subject: Re: Fixing Integrity check errors
Date: Mon, 14 Mar 2022 17:33:02 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

flik <[email protected]> writes:
> What would be the best way to solve integrity errors (unique 
> constraints) caused by a badly done dump/restore? My best guess as 
> ignorant ass, it's simply to dump the current data (only), start a new 
> project, apply the migrations and loading back data.
> Given that the schema is exactly the same, would this work? If so, how 
> can I do it with postgres?
> I already tried to pg_dump --data-only but I keep getting weird errors.

--data-only is really the source of your problem, probably.
If you do a normal (full) pg_dump and restore into an empty
database, then pg_dump should see to loading your data and
installing constraints in the correct order.  With --data-only
it can't make as many guarantees.

Usually, however, that only comes up with foreign key constraints.
If you're seeing unique-constraint failures then there might be
something else going on, such as
* you forgot to make sure the tables are empty before adding data
* or there's something corrupt about the indexes

			regards, tom lane

view thread (2+ messages)

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Fixing Integrity check errors
  In-Reply-To: <[email protected]>

* 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