From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | reina(at)nsi(dot)edu |
Cc: | jwieck(at)debis(dot)com, pgsql-admin(at)postgreSQL(dot)org |
Subject: | Re: [ADMIN] Vacuum command |
Date: | 1998-12-10 21:27:31 |
Message-ID: | m0zoDcS-000EBQC@orion.SAPserv.Hamburg.dsh.de |
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
Not any more. In earlier days, there was a reindexdb command,
which used the bootstrap code to drop and recreate the
indices for the system catalog's. But that disappeared
sometime. I think there's no chance, because dropping of
catalog indices isn't allowed.
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 | Robert Honore | 1998-12-11 16:10:12 | Postgres on Digital UNIX 4.0D |
Previous Message | G. Anthony Reina | 1998-12-10 21:04:18 | Re: [ADMIN] Vacuum command |