aha! no, i didn't check the mem yet. but it seems like it's worth to
buy new ECC-RAM chips, if only ONE SINGLE FAULTY BIT can cause such
trouble!!
thanks for the detailed examination!
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
--------------------------------------------------------
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Henrik Steffen" <steffen@city-map.de>
Sent: Thursday, July 11, 2002 3:50 PM
Subject: Re: [GENERAL] Serious Crash last Friday
> oh, ignore previous message --- it's still too early in the morning.
>
> What you seem to have here is a single bit flip:
>
> Item 109 -- Length: 16 Offset: 6432 (0x1920) Flags: USED
> Block Id: 1048595 linp Index: 3 Size: 16
> Has Nulls: 0 Has Varlenas: 0
>
> 1920: 10001300 03001000 d1930100 02000000 ................
>
> Judging from the surrounding items, the block id in this entry should
> have been 19 (hex 00000013) ... but it's actually 00100013. Everything
> else looks fine on the whole page.
>
> My bet is that you have a bad RAM chip that allowed the bit to flip
> while the index page was in memory. Single-bit changes aren't usually
> what I'd expect from either software bugs or disk-related hardware
> failures.
>
> Have you done anything yet with that memory test program that some other
> folks recommended?
>
> regards, tom lane