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:
>=20
> CREATE SEQUENCE x
> START WITH 1
> INCREMENT BY 1
> NO MAXVALUE
> NO MINVALUE
> CACHE 1;
>=20
> which has the proper value after START WITH. Any ideas why your setup
> is different?
>=20
> -------------------------------------------------------------------------=
--
>=20
> pgsql-bugs@postgresql.org wrote:
> > laurent faillie (l_faillie@yahoo.com) reports a bug with a severity of 2
> > The lower the number the more severe it is.
> >=20
> > Short Description
> > pg_dump problem w/ SEQUENCE
> >=20
> > Long Description
> > Hi all,
> >=20
> > in order to correct bug #899, I have downloaded the current snapshot an=
d I discover a new trouble w/ pg_dump.
> >=20
> > If you have a sequence in your database, pg_dump produce something like=
:
> >=20
> > CREATE SEQUENCE seq_id_fch
> > START WITH=20
> > INCREMENT BY 1
> > MAXVALUE 2147483647
> > NO MINVALUE
> > CACHE 1;
> >=20
> > and psql rise following error :
> >=20
> > ERROR: parser: parse error at or near "WITH" at character 38
> >=20
> > PS: I have downloaded the snapshot monday 24/03/2003
> >=20
> > Bye
> >=20
> > Laurent
> >=20
> >=20
> > Sample Code
> >=20
> >=20
> > No file was uploaded with this report
> >=20
> >=20
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >=20
> > http://www.postgresql.org/docs/faqs/FAQ.html
> >=20
--=20
Rod Taylor <rbt@rbt.ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
