From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Palle Girgensohn <girgen(at)partitur(dot)se> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Patrik Kudo <kudo(at)partitur(dot)se>, "pgsql-sql(at)postgreSQL(dot)org" <pgsql-sql(at)postgreSQL(dot)org> |
Subject: | Re: [SQL] Duplicate tuples with unique index |
Date: | 2000-01-26 00:33:52 |
Message-ID: | 200001260033.TAA04733@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> > > 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Palle Girgensohn | 2000-01-26 00:37:01 | Re: [SQL] Duplicate tuples with unique index |
Previous Message | Palle Girgensohn | 2000-01-26 00:31:42 | Re: [SQL] Duplicate tuples with unique index |