pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomeh, Husam <HTomeh@facorelogic.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Error: duplicate key violates unique constraint - "pg_toast_3270368541_index
Date: Thu, 15 Nov 2007 11:49:44 -0500
Message-ID: <4149.1195145384@sss.pgh.pa.us> (raw)
In-Reply-To: <F1B0F9305B343E43A1C3EECE48B853D501A83DD4@CITGSNA01SXCH02.ana.firstamdata.com>
References: <F1B0F9305B343E43A1C3EECE48B853D501A83DCC@CITGSNA01SXCH02.ana.firstamdata.com>
	<24681.1195105047@sss.pgh.pa.us>
	<F1B0F9305B343E43A1C3EECE48B853D501A83DD4@CITGSNA01SXCH02.ana.firstamdata.com>

"Tomeh, Husam" <HTomeh@facorelogic.com> 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



view thread (4+ messages)

Message-ID: <4149.1195145384@sss.pgh.pa.us>
Permalink:  ../4149.1195145384@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4149.1195145384@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, HTomeh@facorelogic.com
  Subject: Re: Error: duplicate key violates unique constraint - "pg_toast_3270368541_index
  In-Reply-To: <4149.1195145384@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox