Обсуждение: Error: duplicate key violates unique constraint - "pg_toast_3270368541_index
Error: duplicate key violates unique constraint - "pg_toast_3270368541_index
От
"Tomeh, Husam"
Дата:
Hi,
We've started getting duplicate key violates unique constraint error on one of the toast index starting last weekend. This error occurs when attempting to update a huge table.
ERROR: duplicate key violates unique constraint "pg_toast_3270368541_index"
PG version is 8.0 with postgis extension. We're planning to upgrade by end of year though.
select count(*) from pg_toast.pg_toast_3270368541;
count
---------
7663472
count
---------
7663472
We've tried a couple of things:
1) Reprocess the failed extract files by resubmitting them (basically, re-run the updates). It worked so far until today where we retried two times and the update kept failing.
2) R
eindex the toast index but that still did not help. We also run vacuum every night to avoid transaction wraparound limit, so I'm hoping this is error is not related to it..
Is there any workaround to fix this duplicate constraints error? Your assistance is greatly appreciated.
Husam Tomeh
**********************************************************************
This message contains confidential information intended only for the use of the addressee(s) named above and may contain information that is legally privileged. If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message immediately thereafter.
Thank you.
FADLD Tag
**********************************************************************
"Tomeh, Husam" <HTomeh@facorelogic.com> 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
Re: Error: duplicate key violates unique constraint - "pg_toast_3270368541_index
От
"Tomeh, Husam"
Дата:
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? Regards, Husam Tomeh -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Wednesday, November 14, 2007 9:37 PM To: Tomeh, Husam Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error: duplicate key violates unique constraint - "pg_toast_3270368541_index "Tomeh, Husam" <HTomeh@facorelogic.com> 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 ********************************************************************** This message contains confidential information intended only for the use of the addressee(s) named above and may containinformation that is legally privileged. If you are not the addressee, or the person responsible for delivering itto the addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictlyprohibited. If you have received this message by mistake, please immediately notify us by replying to the messageand delete the original message immediately thereafter. Thank you. FADLD Tag **********************************************************************
"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