Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 30 Oct 2006 10:48:41 -0700
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
- References:
- Prev by Date: Re: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
- Next by Date: beta2: process crash: server process (PID 4872) exited with exit code -1073741819
- Previous by thread: Re: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
- Next by thread: beta2: process crash: server process (PID 4872) exited with exit code -1073741819
- Indexes: