Re: Table constraint ordering disrupted by pg_dump - Mailing list pgsql-bugs

From Philip Warner
Subject Re: Table constraint ordering disrupted by pg_dump
Date
Msg-id 3.0.5.32.20010404164947.02627360@mail.rhyme.com.au
Whole thread Raw
In response to Table constraint ordering disrupted by pg_dump  (pgsql-bugs@postgresql.org)
List pgsql-bugs
At 17:51 3/04/01 -0400, Tom Lane wrote:
>
>Rather than using "c.rcname = pg_relcheck.rcname" as part of the match
>condition, consider
...
>it seems to me that lines 2071-2121 in pg_dump.c are largely
>a waste of time

Done and applied.


----------------------------------------------------------------
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   |/

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Table constraint ordering disrupted by pg_dump
Next
From: Karel Zak
Date:
Subject: Re: to_char miscalculation on April Fool's Day, the start of daylight savings