From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | pg_dump doesn't handle CREATE FUNCTIONs well |
Date: | 2001-07-25 02:07:05 |
Message-ID: | 200107250207.f6P275703427@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Rainer Mager (rmager(at)vgkk(dot)com) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
pg_dump doesn't handle CREATE FUNCTIONs well
Long Description
We have a table (table_A) that has a constraint on it that uses a custom function (func_B), which references a different table (table_C). When we do a pg_dump all of the table and function definitions are created correctly but in the wrong order.
The dump has the items in this order: table_C, table_A, func_B
The problem is that the creation of table_A requires the existence of func_B. Therefore the dump should have dumped things in this order: table_C, func_B, table_A.
This is reasonably easy to fix by hand because we only have one such situation and the trail is easy to trace. A more complicated situation could be a pain to fix by hand.
Sample Code
No file was uploaded with this report
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-07-25 06:26:42 | Re: pg_dump doesn't handle CREATE FUNCTIONs well |
Previous Message | pgsql-bugs | 2001-07-24 18:21:02 | insert of date is wrong |