| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pholben(at)greatbridge(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Table constraint ordering disrupted by pg_dump |
| Date: | 2001-04-03 03:14:48 |
| Message-ID: | 3.0.5.32.20010403131448.00c514a0@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
At 16:40 2/04/01 -0400, Tom Lane wrote:
>
>I don't believe this is a bug. There is no guarantee that constraints
>are checked in any particular order.
>
While it't not a bug, it would be nice if pg_dump reproduced definitions as
faithfully as possible. To that end, would it be worth selecting the
constraints in OID order (using oid from pg_relcheck)?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-04-03 03:55:37 | Re: Table constraint ordering disrupted by pg_dump |
| Previous Message | pgsql-bugs | 2001-04-02 23:52:42 | PostgreSQL 7.0.2 Date Miscalculation |