Skip site navigation (1) Skip section navigation (2)

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

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug #564: CREATE TABLE with long table name and long serial column name can cause conflicting sequence naming
Date: 2002-01-21 04:49:45
Message-ID: 200201210449.g0L4njr99285@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Jeff Synnestvedt (jeff(at)refinery(dot)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 (again similiar 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


Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2002-01-21 06:44:55
Subject: Message about not null in ALTER TABLE
Previous:From: Hiroshi InoueDate: 2002-01-21 02:36:40
Subject: Re: [ODBC] odbc error

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group