Bug #564: CREATE TABLE with long table name and long serial column name can cause conflicting sequence naming - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #564: CREATE TABLE with long table name and long serial column name can cause conflicting sequence naming
Date
Msg-id 200201210449.g0L4njr99285@postgresql.org
Whole thread Raw
Responses Re: Bug #564: CREATE TABLE with long table name and long serial column name can cause conflicting sequence naming  (Brent Verner <brent@rcfile.org>)
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: [ODBC] odbc error
Next
From: Reinhard Max
Date:
Subject: 7.2b5 libpq++ include files broken?