Fixing Integrity check errors

From: flik <flikreview(at)gmail(dot)com>
To: pgsql-novice(at)lists(dot)postgresql(dot)org
Subject: Fixing Integrity check errors
Date: 2022-03-14 20:14:55
Message-ID: 9bde7204-1b4c-8702-4593-5afd0607c5d2@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Hi!

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.

Sorry if my message is confusing-confused, I'm quite new with databases!

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2022-03-14 21:33:02 Re: Fixing Integrity check errors
Previous Message Bill Ross 2022-02-22 09:09:02 postgres on pinephone pro (linux phone)?