Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"

From: Rusty Conover <rconover(at)infogears(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
Date: 2006-10-30 09:32:35
Message-ID: DDDCC758-959B-4750-BAFC-8BB0F38C73ED@infogears.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Under a period of high load it seems that creating a temporary tables
with the same name in separate postgres back-ends can trigger this
error:

ERROR: duplicate key violates unique constraint
"pg_type_typname_nsp_index"

The command that causes it is:

create temp table register_reqs(full_key text, register_index
integer) WITHOUT OIDS ON COMMIT DROP

Is this being caused by a race condition? Does the "create table"
command acquire any locks?

# select version();
version
------------------------------------------------------------------------
---------------------------
PostgreSQL 8.1.5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC)
4.1.0 20060304 (Red Hat 4.1.0-3)
(1 row)

This is on Fedora Core 4.

Thanks,

Rusty
--
Rusty Conover
InfoGears Inc.
Web: http://www.infogears.com

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Алексей Заяц 2006-10-30 09:43:43 Re: BUG #2724: Could not check connection status with "ssl=on"
Previous Message Thomas H. 2006-10-29 20:21:05 Re: BUG #2712: could not fsync segment: Permission