Re: pg_dump future problem.

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump future problem.
Date: 2003-05-04 05:49:49
Message-ID: 20030504134835.D44780-100000@houston.familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2003-05-04 07:51:15 Re: pg_dump future problem.
Previous Message Philip Warner 2003-05-04 05:02:21 Re: pg_dump future problem.