Hi,
my experience shows, that such random errors you seem to be suffering from
in postgres are always caused by malfunctioning hardware, be it ram or
harddisk.
I'd suggest to dump the database and put it on another clean server, or if
that is not possible, to change ram and harddisk.
In my case my gdt scsi raid controller seemed to cause bit errors on the
scsi bus, leading to strange behaviour of postgres, which was not logically
explainable. Changing the hdd-subsystem and reinserting the dump was the
solution.
Greetings,
Bjoern
----- Original Message -----
From: Henrik Steffen <steffen@city-map.de>
To: pg <pgsql-general@postgresql.org>
Sent: Friday, July 12, 2002 8:27 AM
Subject: [GENERAL] again trouble
hello all,
another morning, another problem:
select * from zugriffsrechte;
ERROR: find_secondary_indexes: index 14958692 not fount
vacuum verbose analyze zugriffsrechte
ERROR: IndexSupportInitialize: no pg_index entry for index 14958692
tom, could this again be due to a broken SD-RAM chip?
Mit freundlichem Gruß
Henrik Steffen
Geschäftsführer
top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com Tel. +49 4141 991230
mail: steffen@topconcepts.com Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline: +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------