Thread: Bug #564: CREATE TABLE with long table name and long serial column name can cause conflicting sequence naming

Jeff Synnestvedt (jeff@refinery.com) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
CREATE TABLE with long table name and long serial column name can cause conflicting sequence naming

Long Description
When two tables are named with similiar names and those tables also have declarations of a serial column with long
(againsimiliar names) postgresql returns the error(this is the error from my example code when run from psql): 

ERROR:  Relation 'tablewithreal_tableidwithre_seq' already exists

I am running version:

                           version
-------------------------------------------------------------
 PostgreSQL 7.1.3 on i686-pc-linux-gnu, compiled by GCC 2.96
(1 row)

on distribution 7.2 of RedHat linux  kernel 2.4.7-10


Sample Code

CREATE TABLE tablewithreallylongname(
tableidwithreallylongname serial NOT NULL UNIQUE PRIMARY KEY
);


CREATE TABLE tablewithreallylongname2(
tableidwithreallylongname serial NOT NULL UNIQUE PRIMARY KEY
);



No file was uploaded with this report

[2002-01-20 23:49] pgsql-bugs@postgresql.org said:
| Jeff Synnestvedt (jeff@refinery.com) reports a bug with a severity of 3
| The lower the number the more severe it is.
|
| Short Description
| CREATE TABLE with long table name and long serial column name can
| cause conflicting sequence naming

This is a known issue related to the implicit SEQUENCES used for
the SERIAL column types.  There are plans to deal with this in the
7.3 version of postgres.

cheers.
  brent

--
"Develop your talent, man, and leave the world something. Records are
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing."  -- Duane Allman