From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump future problem. |
Date: | 2003-05-04 05:02:21 |
Message-ID: | 5.1.0.14.0.20030504150042.029a97a8@mail.rhyme.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')
)
not sure about CVS.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-05-04 05:49:49 | Re: pg_dump future problem. |
Previous Message | Christopher Kings-Lynne | 2003-05-04 04:14:20 | pg_dump future problem. |