Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67] (may be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id TAA39899 for ; Tue, 25 Jan 2000 19:48:41 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id TAA04733; Tue, 25 Jan 2000 19:33:52 -0500 (EST) From: Bruce Momjian Message-Id: <200001260033.TAA04733@candle.pha.pa.us> Subject: Re: [SQL] Duplicate tuples with unique index In-Reply-To: <388E406E.D591309E@partitur.se> from Palle Girgensohn at "Jan 26, 2000 01:31:42 am" To: Palle Girgensohn Date: Tue, 25 Jan 2000 19:33:52 -0500 (EST) CC: Tom Lane , Patrik Kudo , "pgsql-sql@postgreSQL.org" X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > > 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. Sorry, you have to edit the script to reenable it. -- 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