From: Tom Lane <tgl@sss.pgh.pa.us>
To: Patrik Kudo <kudo@partitur.se>
Cc: pgsql-sql@postgreSQL.org <pgsql-sql@postgresql.org>
Cc: girgen@partitur.se
Subject: Re: [SQL] Duplicate tuples with unique index
Date: Fri, 21 Jan 2000 11:23:02 -0500
Message-ID: <4877.948471782@sss.pgh.pa.us> (raw)
In-Reply-To: <388876AD.A7FE47D3@partitur.se>
References: <388876AD.A7FE47D3@partitur.se>
Patrik Kudo <kudo@partitur.se> writes:
> db=> vacuum ;
> NOTICE: Rel pg_statistic: TID 1/93: OID IS INVALID. TUPGONE 0.
> NOTICE: Index html_text_idx: NUMBER OF INDEX' TUPLES (1193) IS NOT THE
> SAME AS HEAP' (1258)
> ERROR: Cannot insert a duplicate key into a unique index
Given the reference to pg_statistic, I wonder if you aren't getting
burnt by the recently-discovered bug wherein VACUUM ANALYZE tries to
create pg_statistic tuples that are too long. I recommend (a) patch
vacuum.c (see Dirk Lutzebaeck's nearby message); then (b) drop and
recreate html_text_idx; finally (c) DELETE FROM pg_statistic and
then VACUUM ANALYZE to rebuild it. Good luck!
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, kudo@partitur.se, girgen@partitur.se
Subject: Re: [SQL] Duplicate tuples with unique index
In-Reply-To: <4877.948471782@sss.pgh.pa.us>
References: <388876AD.A7FE47D3@partitur.se> <4877.948471782@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