RE: [HACKERS] How to ignore system indexes

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] How to ignore system indexes
Date: 2000-01-18 06:58:23
Message-ID: 002001bf6181$69795ce0$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
>
> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > > -----Original Message-----
> > > From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)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(at)tpf(dot)co(dot)jp(dot)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-18 07:31:26 Re: [HACKERS] Is pg_dump still broken?
Previous Message Micheal H. 2000-01-18 06:39:28 jdbc question