Re: pg_dump future problem. - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: pg_dump future problem.
Date
Msg-id 20030504134835.D44780-100000@houston.familyhealth.com.au
Whole thread Raw
In response to Re: pg_dump future problem.  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: pg_dump future problem.  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
> At 12:14 PM 4/05/2003 +0800, Christopher Kings-Lynne wrote:
> >CREATE TABLE really_long_name (
> >         a SERIAL UNIQUE
> >);
>
> At least in production versions, pg_dump does not do this. It will dump it as
>     a integer default nextval('really_long_na_seq')
> )

No, 7.3 release dumps tables like this.

Assuming that you've use contrib/adddepend to add the dependencies from
your old tables into the dependencies table.  (Which you should do...)

Even if you don't, then any tables you create under 7.3 will certainly be
dumped like that...

Chris



pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: pg_dump future problem.
Next
From: Philip Warner
Date:
Subject: Re: pg_dump future problem.