> >7.4 should hold the fix for
> >pg_dump, although 7.3 has the dependency tracking mechanism.
>
> Which means that in theory we can back-patch them for 7.3.1.
Not wanting to get too involved in discussions as to whether this should
be done or not, I would recommend you nice chaps save your stren
At 01:51 PM 15/11/2002 -0500, Rod Taylor wrote:
7.4 should hold the fix for
pg_dump, although 7.3 has the dependency tracking mechanism.
Which means that in theory we can back-patch them for 7.3.1.
Philip Warner
> If you know how this problem might be fixed, list the solution below:
> -
>
> Dump all functions and types before indexes
This causes errors in other ways. The true solution is to have pg_dump
use a decent dependency tracking
POSTGRESQL BUG REPORT TEMPLATE
Your name : Robert John Shepherd
Your email address : [
Hey all,
pg_dump fails to output necessary CREATE SEQUENCE statements unless
the SERIAL column is named "id" when called with the '-t tablename'
switch. When '-t' is not specified, the CREATE SEQUENCE statements
do get output.
wishing-I'd-noticed-this-Friday-nite-ly y'rs,
brent
Observerat
PGSQL-BUGS:
I recently did a pg_dump of my data from 7.0 and did an upgrade to
7.0.2.
Then I did a: psql "database name" -f "my sql dump file"
The problem is that a table was created that uses a funtion, which
function had not yet been created.
(The function is created later on in the dump file
