Re: pg_group_name_index corrupt? - Mailing list pgsql-hackers

On Thu, 4 May 2000, Tom Lane wrote:

> But backend 2 doesn't:
> 
> other=# vacuum analyze pg_group;
> NOTICE:  Index pg_group_sysid_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (1).
>         Recreate the index.
> NOTICE:  Index pg_group_name_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME
> AS HEAP' (1).
>         Recreate the index.
> VACUUM
> 
> pg_shadow would have the same problem if it had indices, which I thought
> it did but they seem to have been disabled.
> 
> Can you say "one more initdb"?  I knew you could...

Would a pg_upgrade fix this, or do I have to do a whole dump/reload?  

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org