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

From: Rusty Conover <rconover(at)infogears(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
Date: 2006-10-30 17:48:41
Message-ID: 2CE290BD-8E17-4884-B432-48FDBFF53EB4@infogears.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On Oct 30, 2006, at 7:56 AM, Tom Lane wrote:

> Rusty Conover <rconover(at)infogears(dot)com> writes:
>> 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"
>
> Can you create a reproducible test case?
>
> regards, tom lane

Hi Tom,

I'm able to reproduce it. It's happened twice in the last 8 hours.
I'm not yet able to provide an easy to trigger test case.

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas H. 2006-10-31 00:30:22 beta2: process crash: server process (PID 4872) exited with exit code -1073741819
Previous Message Tom Lane 2006-10-30 14:56:22 Re: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"