Fixing db after missing index

From: Maarten Boekhold <maarten(dot)boekhold(at)tibcofinance(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Fixing db after missing index
Date: 2000-04-17 07:45:23
Message-ID: 38FAC113.9CD59784@tibcofinance.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,

Yesterday I needed to do a big update to one of our databases, and as I always
do
with big updates, I first deleted the indices for the main table (it's faster
this
way). However, one index failed to delete cos the disk file was gone. Dunno
what happened, but I suppose I brought that one on myself.

Anyway, instead of being smart and doing 'touch index_file', I decided to mess
around
in the system tables. So I deleted that index from pg_class and pg_index. This
helped, I could use the table again (it had become unusable), and recreated
the indices.

Despite it working correctly now, I still get a message relating to the old
index when I do a vacuum. The first time I got an error message, before I
messed around with pg_class and pg_index, the message included an oid number,
which I have written down. I searched tru the other system tables, and foung
one other reference to that number, in pg_attribute. Should I delete that row
too? More generally, which tables reference an index?

Maarten

--

Maarten Boekhold, maarten(dot)boekhold(at)tibcofinance(dot)com
TIBCO Finance Technology Inc.
"Sevilla" Building
Entrada 308
1096 ED Amsterdam, The Netherlands
tel: +31 20 6601000 (direct: +31 20 6601066)
fax: +31 20 6601005
http://www.tibcofinance.com

Responses

  • Maintenance at 2000-04-17 11:25:53 from Raul Carvalho

Browse pgsql-admin by date

  From Date Subject
Next Message Raul Carvalho 2000-04-17 11:25:53 Maintenance
Previous Message Joe Conway 2000-04-17 03:02:32 pg_dump error