pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Palle Girgensohn <girgen@partitur.se>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: 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: Wed, 26 Jan 2000 01:31:42 +0100
Message-ID: <388E406E.D591309E@partitur.se> (raw)
References: <200001252008.PAA20686@candle.pha.pa.us>

Bruce Momjian wrote:
> 
> > 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.

Nope. pg_upgrade was "disabled in this release because the internal blahblahblah disk layout changed from previous versions". cat /dev/null > pg_statistic didn't help, and the file was already zero
bytes long.

Applied the patches to vacuum.c and hio.c, and pg_dumpall && initdb && psql < dump.sql fixed it.

Thanks for your support! 

/Palle



view thread (13+ messages)  latest in thread

Message-ID: <388E406E.D591309E@partitur.se>
Permalink:  ../388E406E.D591309E@partitur.se/
Also on:    postgresql.org/message-id/388E406E.D591309E@partitur.se

 · 

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: girgen@partitur.se, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, kudo@partitur.se
  Subject: Re: [SQL] Duplicate tuples with unique index
  In-Reply-To: <388E406E.D591309E@partitur.se>
  References: <200001252008.PAA20686@candle.pha.pa.us> <388E406E.D591309E@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