| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | soumitra(dot)bhandary(at)hotmail(dot)com |
| Cc: | Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Pg_restore failing due to data inconsistency in dump file |
| Date: | 2018-12-13 15:25:48 |
| Message-ID: | CAKFQuwY8n=cM3BxKSVX73MLuWDAHeB7gwpwQOjwQHHU4W4vA_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Dec 13, 2018 at 7:26 AM soumitra bhandary <
soumitra(dot)bhandary(at)hotmail(dot)com> wrote:
> But this one is third party application and dump is restored from dump
> file not plain text file . So is there any way to control it ?
>
Your backup file (and the source database is comes from) is corrupted.
You need to decide whether you want to restore that backup anyway; or just
throw it away, fix the source database, and generate a new backup file.
If you want to do the former you will want to restore schema only. Modify
the schema by dropping the foreign key. Restore the data. Fix the newly
restored data. Recreate the foreign key.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Artem Tomyuk | 2018-12-14 10:40:27 | pg_attribute getting bloated in size |
| Previous Message | soumitra bhandary | 2018-12-13 14:57:01 | Re: Pg_restore failing due to data inconsistency in dump file |