From: Tom Lane <tgl@sss.pgh.pa.us>
To: Palle Girgensohn <girgen@partitur.se>
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 11:26:12 -0500
Message-ID: <13944.948817572@sss.pgh.pa.us> (raw)
In-Reply-To: <388DC939.1335143@partitur.se>
References: <388876AD.A7FE47D3@partitur.se>
<4877.948471782@sss.pgh.pa.us>
<388DC939.1335143@partitur.se>
Palle Girgensohn <girgen@partitur.se> writes:
> 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
Ugh. Yup, your pg_statistic table is corrupted all right.
What you may have to do is pg_dump that database, destroydb/createdb,
and reload.
I have a possible shortcut for you, but I *strongly* suggest that you
pg_dump first in case it doesn't work! After making your backup dump,
stop the postmaster and truncate the broken database's pg_statistic
file to zero length:
cp /dev/null .../data/base/yourdb/pg_statistic
Then restart the postmaster and see if you can vacuum analyze the
broken database. If so, you are good to go; if not, it's time to
reload that database.
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, girgen@partitur.se, kudo@partitur.se
Subject: Re: [SQL] Duplicate tuples with unique index
In-Reply-To: <13944.948817572@sss.pgh.pa.us>
References: <388876AD.A7FE47D3@partitur.se> <4877.948471782@sss.pgh.pa.us> <388DC939.1335143@partitur.se> <13944.948817572@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