Re: Bug #755: Error on create a new sequence by using the

7.3 will partially fix this issue by extending the length of the NAME
data type.

Ie.  You won't hit it until you have large (32+ character) length names.

On Tue, 2002-09-03 at 16:31, pgsql-bugs@postgresql.org wrote:
> S=F8ren Laursen (sl@scrooge.dk) reports a bug with a severity of 2
> The lower the number the more severe it is.
>=20
> Short Description
> Error on create a new sequence by using the create table command.
>=20
> Long Description
> In postgresql 7.1 and 7.2.1:
>=20
> Then using a statement like:
> CREATE TABLE longtablename(
> longtablenamenr serial NOT NULL UNIQUE PRIMARY KEY,....
>=20
> )
>=20
> and later a=20
> CREATE TABLE longtablenamestep(
> longtablenamestepnr serial NOT NULL UNIQUE PRIMARY KEY,....
>=20
> )
>=20
> I get an error on creating the last table. This is because the new sequen=
ce is named with the same name as the one used by the first table. The crea=
te statement is then terminated and no table is created. I would have to cr=
eate the sequence my self and then create the table using statements like:
>  not null default nextval('"longtablename_longtablename_sq1"'::text).
>=20
> Regards,
>=20
> Soeren Laursen
>=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/users-lounge/docs/faq.html
>=20