Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 9E9022E28AD for ; Thu, 15 Nov 2007 12:49:49 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 29086-08 for ; Thu, 15 Nov 2007 12:49:29 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 7B1162E2368 for ; Thu, 15 Nov 2007 12:49:46 -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 lAFGni7U004150; Thu, 15 Nov 2007 11:49:44 -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: <24681.1195105047@sss.pgh.pa.us> Comments: In-reply-to "Tomeh, Husam" message dated "Thu, 15 Nov 2007 08:16:35 -0800" Date: Thu, 15 Nov 2007 11:49:44 -0500 Message-ID: <4149.1195145384@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/151 X-Sequence-Number: 27394 "Tomeh, Husam" writes: > Thanks Tom. As a temporarily solution though, would reorging the table > (pgdump,drop/truncate, reload) resolve the OID collision issue and buy > us some time until we get the upgrade going? Probably. I wouldn't bother with pg_dump, just INSERT ... SELECT the data into a new table and then rename that one into place. regards, tom lane