Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in

From: "Rainer Tammer" <pgsql(at)spg(dot)schulergroup(dot)com>
To: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in
Date: 2002-02-09 06:58:55
Message-ID: 200202090659.HAA11353@gatekeeper.schuler.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello,

On Fri, 8 Feb 2002 11:32:50 -0800 (PST), Stephan Szabo wrote:

>
>On Fri, 8 Feb 2002 pgsql-bugs(at)postgresql(dot)org wrote:
>
>> 2. tables with complex foreign key constrains will not be imported
>
>I probably couldn't help with the other question, but...
>
>What do you mean by this? Does it error on the creation, does it
>make the tables but not the constraints?
>

Unfortunately I get creation errors on a couple of tables.
As a result the table and the data are missing in the new 7.2 DB.

I think the problem is, that the order in which the tables / constrains are
exported is not coerect.

Postgres tries to import the tables in the wrong order.

Example:

Table A depends on table B.
Unfortunately table B will be imported AFTER table A.
Result: table A will not be imported; the date from table A will not be importet.

Bye
Rainer Tammer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2002-02-10 23:48:28 Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in 7.2.0
Previous Message Stephan Szabo 2002-02-08 19:32:50 Re: Bug #578: pg_dumpall from 7.1.3 can not be imported in