From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Pg_restore failing due to data inconsistency in dump file
Date: Thu, 13 Dec 2018 08:27:49 -0600
Message-ID: <3814e222-b3cc-2a0b-cf26-fd9057a1c498@gmail.com> (raw)
In-Reply-To: <CAGDYbUOtHcy_sLs5fJxoX0_=c4uos25JL3CKv6Vpp=FCf95K0A@mail.gmail.com>
References: <MA1PR0101MB16876D291572530CED5E798DE0A00@MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM>
<CAGDYbUOtHcy_sLs5fJxoX0_=c4uos25JL3CKv6Vpp=FCf95K0A@mail.gmail.com>
No. That is *not* the first thing to do.
OP needs to find out how the corruption got into the source in the first
place. There's probably corruption in one of the indexes in
user_role_mapping anduser_entity which support fk_5hrm2vlf9ql5fu043kqepovbr.
On 12/13/2018 06:21 AM, Shreeyansh Dba wrote:
> Hi Soumitra,
>
> Normally this type of error encounter while insert or update data on the
> table, which is dependable on the other table data.
>
> To avoid such error you should disable foreign keys before insert data and
> enable it later.
>
> <http://www.shreeyansh.com;
>
> On Thu, Dec 13, 2018 at 4:50 PM soumitra bhandary
> <soumitra.bhandary@hotmail.com <mailto:soumitra.bhandary@hotmail.com>> wrote:
>
> Hello Team ,
>
> I have encountered following issue while restoring the Postgres dump
> using pg_restore . Please provide any suggestion to the same .
>
> 1. This dump was taken using bdr_dump as bdr enabled database and all
> the BDR configuration and extension was excluded .
> 2. DUMP was taken in a running DB server where BDR was running .
> 3. Postgres Dump was taken in .dump format .
> 4. During restoration of the same using pg_restore getting following
> error .
>
> Error :
>
> pg_restore:[archiver (db)]Error from TOC entry 3061; 2606 17551 FK
> CONSTRAINT fk_5hrm2vlf9ql5fu043kqepovbr DBNAME
> pg_restore:[archiver (db)]could not execute query: ERROR: insert or
> update on table "user_attribute" violates foreign key constraint
> "fk_5hrm2vlf9ql5fu043kqepovbr"
> DETAIL: Key (user_id)=(1f34ec07-7087-45ff-8a56-f36177752499) is not
> present in table "user_entity".
> Command was: ALTER TABLE ONLY user_attribute
> ADD CONSTRAINT fk_5hrm2vlf9ql5fu043kqepovbr FOREIGN KEY (user_id)
> REFERENCES user_entity...
> pg_restore:[archiver (db)]Error from TOC entry 3065; 2606 17601 FK
> CONSTRAINT fk_c4fqv34p1mbylloxang7b1q3l DBNAME
> pg_restore:[archiver (db)]could not execute query: ERROR: insert or
> update on table "user_role_mapping" violates foreign key constraint
> "fk_c4fqv34p1mbylloxang7b1q3l"
> DETAIL: Key (user_id)=(24d1ee2a-b05e-4c30-a292-84045c47611e) is not
> present in table "user_entity".
>
>
> Thanks ,
>
> Soumitra
>
>
--
Angular momentum makes the world go 'round.
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-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Pg_restore failing due to data inconsistency in dump file
In-Reply-To: <3814e222-b3cc-2a0b-cf26-fd9057a1c498@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox