Re: [ADMIN] Vacuum command

That makes sense. Is there a way that is less drastic than dumping,
re-initdb, and reloading the database? It would probably take a day or
two to do this. Does anybody know if I can fix the catalog in another
way?

-Tony

Jan Wieck wrote:

>
>     That  behaviour  reminds  me of a similar situation, where an
>     index of one of the user tables was corrupt,  causing  vacuum
>     to loop on that (all blocks cached so no HD activity).
>
>     Dropping/recreating   the   index  in  question  solved  that
>     problem.
>
>     But the difference this time is that it does not  occur  when
>     you  manually vacuum all the user tables. So if it's the same
>     reason (corrupt index), this time it must be one of a  system
>     catalog.
>
>     Can you dump/initdb/reload your database?
>
> Jan
>
> --
>
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me.                                  #
> #======================================== jwieck@debis.com (Jan Wieck) #