>
> 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 comman
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 situati
>
> I've had trouble in the past with the vacuum command taking a long time
> to complete. This past vacuum went for 5 days before I CTRL-C'd it. I'm
> wondering if there is a bug.
>
> I have PostgreSQL 6.3.2 on a Red Hat 5.1 system (PII/400 MHz, 256 Meg
> RAM, 512 Meg Swap, 18 Gig Hard Ultra-wide
I've had trouble in the past with the vacuum command taking a long time
to complete. This past vacuum went for 5 days before I CTRL-C'd it. I'm
wondering if there is a bug.
I have PostgreSQL 6.3.2 on a Red Hat 5.1 system (PII/400 MHz, 256 Meg
RAM, 512 Meg Swap, 18 Gig Hard Ultra-wide SCSI Drive).
