Hello, Our development DB server had a faulty power supply, we replaced it got everything running again. However, when I try to vacuum the database it uses all of the CPU and eventually crashes postgres. We're running Postgres 6.5.3 on FreeBSD 3.3R. The DB server is a PII/300, 256MB Ram. I then went through table by table vacuuming one at a time. I found the table that seems to "blow up" the server. The errors I get: NOTICE: Rel cust_data: TID 121/44: OID IS INVALID. TUPGONE 1. NOTICE: Rel cust_data: TID 121/62: OID IS INVALID. TUPGONE 0. NOTICE: Rel cust_data: TID 121/74: OID IS INVALID. TUPGONE 1. NOTICE: Rel cust_data: TID 121/92: OID IS INVALID. TUPGONE 1. NOTICE: Rel cust_data: TID 121/98: OID IS INVALID. TUPGONE 1. Postgres eventually cores. Looking through the archives I found that people had to basically kill the DB and reload it in order to rebuild the indices. Is this still the case? Is there any way to "force" the indices to rebuild? Is there something else I'm missing? Thanks in advance! KC [EMAIL PROTECTED] ************
