From: Palle Girgensohn <girgen@partitur.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Patrik Kudo <kudo@partitur.se>
Cc: pgsql-sql@postgreSQL.org <pgsql-sql@postgreSQL.org>
Subject: Re: [SQL] Duplicate tuples with unique index
Date: Tue, 25 Jan 2000 17:03:05 +0100
Message-ID: <388DC939.1335143@partitur.se> (raw)
References: <388876AD.A7FE47D3@partitur.se>
<4877.948471782@sss.pgh.pa.us>
Tom Lane wrote:
>
> 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
>
> ************
Unfotunately, it doesn't quite work:
pp=> vacuum analyze;
NOTICE: Rel pg_statistic: TID 1/93: OID IS INVALID. TUPGONE 0.
VACUUM
pp=> delete from pg_statistic;
ERROR: heap_delete: (am)invalid tid
pp=>
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: girgen@partitur.se, tgl@sss.pgh.pa.us, kudo@partitur.se
Subject: Re: [SQL] Duplicate tuples with unique index
In-Reply-To: <388DC939.1335143@partitur.se>
References: <388876AD.A7FE47D3@partitur.se> <4877.948471782@sss.pgh.pa.us> <388DC939.1335143@partitur.se>
* 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