It's my bad. Has to do with the sequence having the default value and *NOT* having been called.
See -patches for update to simply skip START WITH in that case. On Tue, 2003-03-25 at 10:08, Bruce Momjian wrote: > I just did 'CREATE SEQUENCE x' and pg_dump produced: > > CREATE SEQUENCE x > START WITH 1 > INCREMENT BY 1 > NO MAXVALUE > NO MINVALUE > CACHE 1; > > which has the proper value after START WITH. Any ideas why your setup > is different? > > --------------------------------------------------------------------------- > > [EMAIL PROTECTED] wrote: > > laurent faillie ([EMAIL PROTECTED]) reports a bug with a severity of 2 > > The lower the number the more severe it is. > > > > Short Description > > pg_dump problem w/ SEQUENCE > > > > Long Description > > Hi all, > > > > in order to correct bug #899, I have downloaded the current snapshot and I > > discover a new trouble w/ pg_dump. > > > > If you have a sequence in your database, pg_dump produce something like : > > > > CREATE SEQUENCE seq_id_fch > > START WITH > > INCREMENT BY 1 > > MAXVALUE 2147483647 > > NO MINVALUE > > CACHE 1; > > > > and psql rise following error : > > > > ERROR: parser: parse error at or near "WITH" at character 38 > > > > PS: I have downloaded the snapshot monday 24/03/2003 > > > > Bye > > > > Laurent > > > > > > Sample Code > > > > > > No file was uploaded with this report > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 5: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/docs/faqs/FAQ.html > > -- Rod Taylor <[EMAIL PROTECTED]> PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
