Oh, good. I was under the impression that 7.1.3 didn't have reindex
(that's was Jean said at first, and I haven't used it in so long, I wasn't
sure either.)
Jean, don't forget to BACKUP first.
On Wed, 25 Jun 2003, Martijn van Oosterhout wrote:
> On Wed, Jun 25, 2003 at 04:14:10AM -0600, scott.marlowe wrote:
> > Looks like you'll have to dump and restore your database. :-(
>
> Nothing so drastic. 7.1 has reindex (7.0 has to 7.1 must have it too). To do
> it on system indexes you need to run it as single user mode. Start the
> a postgres process with -P which allows you to reindex system indexes.
> Probably drop them too, if you want to.
>
> > On Wed, 25 Jun 2003, Jean-Christophe ARNU wrote:
> >
> > > Le Wed, 25 Jun 2003 03:25:46 -0600 (MDT)
> > > "scott.marlowe" <scott.marlowe@ihs.com> me disait que :
> > >
> > > > Drop and recreate the index is your only solution given the constraints
> > > > you have.
> > > >
> > >
> > > Thanks for your quick answer. :)
> > >
> > > I agree on this procedure to get rid of the reluctant indices but as
> > > pg_statistic_relid_att_index is a system index it seems to put another problem
> > > in the bucket : An error occurs when I try to remove this index....
> > >
> > > supervisor=# drop index pg_statistic_relid_att_index;
> > > ERROR: index "pg_statistic_relid_att_index" is a system index
> > >
> > > If I try to do the same on template1 database, I get the same result :/
> > >
> > >
> > > Regards
> > >
> > >
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister command
> > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
