> > I know I can fix this by recreating the indexes, but I don't know how to
> > do it for a system table and if it's safe.
> > Any hints ?
> Unfortunately, this is a bug in PostgreSQL with respect to system
> indexes. You can safely drop/create user indexes, but not system
> ones. The only way to reclaim the space used is to dump/reload
> your database. Under 7.0, I *believe* Hiroshi's REINDEX command
> (please correct me someone if I'm wrong) will allow you to
> reconstruct system indexes, but the root problem still exists...
pg_upgrade will allow this, without dump/reload of data.
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
In response to
pgsql-hackers by date
|Next:||From: Hiroshi Inoue||Date: 2000-04-04 23:59:35|
|Subject: RE: CURSOR after hitting end|
|Previous:||From: Mike Mascari||Date: 2000-04-04 20:22:56|
|Subject: Re: Indexes growing continuously|