Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index
Date
Msg-id 20040110002011.GA5784@svana.org
Whole thread Raw
In response to ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index  (Kragen Sitaker <kragen+pgsql@airwave.com>)
Responses Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index
List pgsql-general
On Fri, Jan 09, 2004 at 12:07:25PM -0800, Kragen Sitaker wrote:
<snip>

Not really related to your problem, but given you're in a transaction, why
do you need to lock anything? What's wrong with:

> The daemon that gets this error does the following every 15 seconds:
> - start a transaction
> - delete the contents of the other table
> - execute a complex and sometimes slow SELECT INTO query, creating a
>   temporary table
> - copy the contents of the temporary table into the other table
> - drop the temporary table (again, embarrassing, sorry)
> - commit

Maybe I'm missing something?
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> (... have gone from d-i being barely usable even by its developers
> anywhere, to being about 20% done. Sweet. And the last 80% usually takes
> 20% of the time, too, right?) -- Anthony Towns, debian-devel-announce

Attachment

pgsql-general by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: no space left on device
Next
From: "Nigel J. Andrews"
Date:
Subject: Re: no space left on device