Thread: 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 --------------------------------------------------------
Attachment
On Fri, 2002-07-12 at 08:27, Henrik Steffen wrote: > 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? Yep! Sounds like the problem I had last summer with bad RAM Cheers Tony Grant -- RedHat Linux on Sony Vaio C1XD/S http://www.animaproductions.com/linux2.html Macromedia UltraDev with PostgreSQL http://www.animaproductions.com/ultra.html
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 --------------------------------------------------------
I must suggest Memtest86 (http://www.memtest86.com). It is extrememly good at picking up dodgy RAM, even if it's a single bit error that only occurs under certain conditions. On Fri, Jul 12, 2002 at 08:27:55AM +0200, Henrik Steffen wrote: > > 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? -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > There are 10 kinds of people in the world, those that can do binary > arithmetic and those that can't.
"Henrik Steffen" <steffen@city-map.de> writes:
> 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?
Perhaps. It's certainly looking more and more like you've got some
kind of hardware problem ... Postgres is just not this flaky for most
people ;-).
If you wanted to dig into it, you could pg_filedump
pg_index_indrelid_index and look to see why it doesn't have an entry for
14958692. My bet is that the entry is indeed there, but is not being
found --- either its own key is corrupted, or some nearby keys are
corrupted in a way that renders them out-of-order, causing binary search
to conclude the desired key is not present. A single-bit error in the
key field would certainly suffice to cause such a problem.
regards, tom lane