-----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
>
> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > > -----Original Message-----
> > > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> > >
> > > > > One solution is to use pg_upgrade. It allows an initdb and
> > > recreate of
> > > > > all tables without reload.
> > > > > --
> > > >
> > > > Isn't it a big charge to execute pg_upgrade for a huge database ?
> > > > I have never used pg_upgrade.
> > > > Is pg_upgrade available now ?
> > > > Is pg_upgrade reliable ?
> > >
> > > It has been around since 6.3? It allows initdb, recreates the tables,
> > > then moves the data files back into place. There is even a
> manual page.
> > >
> >
> > I know the command but does 6.5 have it ?
>
> Sure, but it is disabled in 6.5 because we changed the binary table
> format from 6.4 to 6.5. However, I have already recommended people use
> it who have broken system indexes, and it worked.
>
It seems pg_upgrade is too complicated to recover system indexes.
In addtion,could pg_upgrade/pg_dump/vacuum etc ... work even when
a critical system index is broken ?
Regards.
Hiroshi Inoue
Inoue@tpf.co.jp.