Re: pg_dump - wrong order with inheritance

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: pinker <pinker(at)onet(dot)eu>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_dump - wrong order with inheritance
Date: 2015-11-23 13:06:26
Message-ID: CAB7nPqTe1-Gm4MAytDQO2fvHa55k63YoxCy+QSSZJO4nOawjvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Nov 23, 2015 at 9:27 PM, pinker <pinker(at)onet(dot)eu> wrote:
> Some tables are inherited. Maybe it's the issue with right order by inheritance? Maybe I can somehow force another order?

pg_dump is usually able to take care of that automatically and dumps
the data in an order that makes sense by looking at the tree
dependency of relations. One way that would allow you to bypass this
error in any case is to use pg_dump --disable-triggers so as those
integrity checks are disabled when loading the data. This will add in
the dump the necessary commands to do so, thought reloading the dump
will need superuser rights.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message zsolt.sandor 2015-11-23 13:42:52 BUG #13781: "unrecognized node type" errors
Previous Message Caleb Meredith 2015-11-23 13:05:51 Re: BUG #13780: Multiple commands not allowed for creating a policy.