Re: [GENERAL] Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071)ISNOT THE SAME AS HEAP' (1070) - Mailing list pgsql-general

From Mike Mascari
Subject Re: [GENERAL] Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071)ISNOT THE SAME AS HEAP' (1070)
Date
Msg-id 38608A02.A82383C3@mascari.com
Whole thread Raw
In response to Re: [GENERAL] Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071)IS NOT THE SAME AS HEAP' (1070)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [GENERAL] Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071)ISNOT THE SAME AS HEAP' (1070)
List pgsql-general
Bruce Momjian wrote:
>
> > Bruce Momjian wrote:
> >
> > > > Anyone seen this message or know what it means?
> > > >
> > > > NOTICE:  Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071) IS
> > > > NOT THE SAME AS HEAP' (1070)
> > >
> > > Drop index and recreate.  Next release will be more specific in error
> > > message.
> >
> > I have no idea *which* index to drop/recreate, and I have hundreds of them.
> > Ouch.
>
> That will also be fixed.

I thought that the index in question was, in fact,
pg_proc_prosrc_index in the above example. If that's the
case, then is it possible for Ed to rebuild a system index?
The only absolutely surefire way is to dump/reload, isn't
it? Maybe somewhere someone is doing a heap_insert(),
heap_replace(), et al, and an event is happening which is
causing the code to not get to the
CatalogOpenIndices()/CatalogIndexInsert()/CatalogCloseIndices()...

Just curious,

Mike Mascari

pgsql-general by date:

Previous
From: Kevin Lo
Date:
Subject: Re: [INTERFACES] Announce: PostgreSQL-6.5.3 binaries available forWindows NT
Next
From: Mike Mascari
Date:
Subject: Re: [GENERAL] item descriptions in psql