pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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 15:08:46 -0500 (EST)
Message-ID: <200001252008.PAA20686@candle.pha.pa.us> (raw)
In-Reply-To: <13944.948817572@sss.pgh.pa.us>

> 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.
> 

Running pg_upgrade is another option.


-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (13+ messages)  latest in thread

Message-ID: <200001252008.PAA20686@candle.pha.pa.us>
Permalink:  ../200001252008.PAA20686@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200001252008.PAA20686@candle.pha.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 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: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, girgen@partitur.se, kudo@partitur.se
  Subject: Re: [SQL] Duplicate tuples with unique index
  In-Reply-To: <200001252008.PAA20686@candle.pha.pa.us>
  References: <13944.948817572@sss.pgh.pa.us> <200001252008.PAA20686@candle.pha.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