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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Rusty Conover <rconover(at)infogears(dot)com>
- 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 09:56:22 -0500
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
- Follow-Ups:
- References:
- Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
- From: Rusty Conover
- Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
- Prev by Date: Re: BUG #2724: Could not check connection status with "ssl=on"
- Next by Date: Re: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
- Previous by thread: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
- Next by thread: Re: Bug: ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
- Indexes: