From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
---|---|
To: | Johannes Meidert <johannes(dot)meider(at)rohde-schwarz(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5698: pg_dump (8.3.11) does not consider constrains |
Date: | 2010-10-08 14:03:38 |
Message-ID: | 4caf24be.08c88e0a.3edd.ffffd7b6@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Oct 08, 2010 at 11:46:31AM +0000, Johannes Meidert wrote:
> pg_dump dumps tables in the worng order for constraints (table a refrences
> key of table b, but table a is dumped first). As a consequence an import
> fails, because the required foreign key (in table b) is missing when table a
> is imported.
> Work around: import twice.
> Is this fixed in version 9.0?
Could you give details of exactly what pg_dump commands you used? By default
pg_dump dumps tables and data without any constraints first, and then adds
constraints in a valid order. If, however, you do something like dump the
schema first, and then dump data into that schema, there's little pg_dump can
do to avoid problems such as you describe.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua Tolley | 2010-10-08 14:14:19 | Re: BUG #5700: double-quoting column names |
Previous Message | Piergiorgio Buongiovanni | 2010-10-08 12:20:35 | BUG #5700: double-quoting column names |