I concur with this, I had *exactly* this problem. My hardware vendor
overclocked my intel cpu, which was fine when it was an NT box because NT
thrashes on the disk.
But when running postgres on Linux on that machine (we had to put more
hardware behind NT) the hardware test utilities all showed good hardware,
but there were random bit errors that went away when I removed the
overclocking. NT never encountered that because it was choking on disk I/O,
not on CPU cycles.
Terry Fielder
Manager Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Kevin Brown
> Sent: Monday, December 16, 2002 6:15 PM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Total crash of my db-server
>
>
> Henrik Steffen wrote:
> > In my opinion, postgresql does something on my machine
> > that leads to these complete system lockups.
>
> PostgreSQL might beat on the disk subsystem hard enough to show faults
> in it, or perhaps it uses enough CPU that the CPU isn't being cooled
> properly anymore, etc.
>
> But regardless, that only means that PostgreSQL is a trigger, not an
> actual root cause. And it means that you will almost certainly have
> problems even after switching database engines.
>
> You mentioned that you're using a hardware RAID controller. There is
> always the possibility that the driver for that controller isn't
> entirely stable.
>
> If you have an identical box you can drop in place, I highly recommend
> that you do so. I'm betting that your problems will disappear after
> you do that.
>
>
> --
> Kevin Brown
kevin@sysexperts.com
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo@postgresql.org
>
