Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 8B63B2E2D95 for ; Thu, 15 Nov 2007 01:37:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 31971-05 for ; Thu, 15 Nov 2007 01:37:30 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 4D5C22E2D8E for ; Thu, 15 Nov 2007 01:37:30 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lAF5bRZ6024682; Thu, 15 Nov 2007 00:37:27 -0500 (EST) To: "Tomeh, Husam" cc: pgsql-admin@postgresql.org Subject: Re: Error: duplicate key violates unique constraint - "pg_toast_3270368541_index In-reply-to: References: Comments: In-reply-to "Tomeh, Husam" message dated "Wed, 14 Nov 2007 17:32:21 -0800" Date: Thu, 15 Nov 2007 00:37:27 -0500 Message-ID: <24681.1195105047@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/133 X-Sequence-Number: 27376 "Tomeh, Husam" writes: > We've started getting duplicate key violates unique constraint error on > one of the toast index starting last weekend. > PG version is 8.0 with postgis extension. Consider updating to something more recent. That problem was addressed in this 8.1-cycle patch: http://archives.postgresql.org/pgsql-committers/2005-08/msg00109.php regards, tom lane