From: | "G(dot) Anthony Reina" <reina(at)nsi(dot)edu> |
---|---|
To: | Jan Wieck <jwieck(at)debis(dot)com>, "pgsql-admin(at)postgreSQL(dot)org" <pgsql-admin(at)postgreSQL(dot)org> |
Subject: | Re: [ADMIN] Vacuum command |
Date: | 1998-12-10 21:04:18 |
Message-ID: | 36703752.911A3B17@nsi.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1998-12-10 21:27:31 | Re: [ADMIN] Vacuum command |
Previous Message | Jan Wieck | 1998-12-10 21:01:46 | Re: [ADMIN] Vacuum command |