| From: | Brook Milligan <brook(at)trillium(dot)NMSU(dot)Edu> |
|---|---|
| To: | hackers(at)postgreSQL(dot)org |
| Subject: | pgdump and sequences |
| Date: | 1999-01-10 02:50:50 |
| Message-ID: | 199901100250.TAA17457@trillium.nmsu.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've just migrated a database to 6.4.2 and was looking at the new
pgdump output. It looks much better than earlier versions, but it
doesn't seem to include any information about sequences created
implicitly via the serial datatype. Pgdump describes the field as one
might have before (e.g., int4 default nextval (table_id_seq)), but the
sequence is never created. As a result, the script seems unable to
recreate the state of the database.
What is required to fix this? Should this be a TODO item?
Cheers,
Brook
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl Eichwalder | 1999-01-10 09:34:50 | Re: TCL/TK configure problems |
| Previous Message | Bruce Momjian | 1999-01-10 01:47:46 | Re: [HACKERS] RE: [GENERAL] Benchmarking PGSQL against Microsoft SQL 7 |