Re: Multiple Crashs on OSX Intel

Hi,

Marc is unavailable today so I take over in order to move forward with our
crash issue.

Tom, it is very unlikely that the issue is located with the hardware as we
tested on 2 brand new hardware and both exibit exactly the same symptoms
despite they are differents models...

Would you have any other idea of where to look for the cause of these crash?
For example would it be possible that the crash would be caused by some
system library rather than the postgres code itself?
Also, is there any debugging option we could turn on on the faulty systems
in order to pin point where is located the bug?

Thanks a million for your help.

Best regards.
Fabrice

> De : Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Date : Thu, 01 Feb 2007 12:29:01 -0500
> À : Marc Simonin <m(dot)simonin(at)allibert-trekking(dot)com>
> Cc : <pgsql-ports(at)postgresql(dot)org>
> Objet : Re: [PORTS] Multiple Crashs on OSX Intel
>
> Marc Simonin <m(dot)simonin(at)allibert-trekking(dot)com> writes:
>> But I put here one of the Crash logs and put attached the gzipped entire
>> Crashlog file (if it pass through the mailing list !).
>
> Wow, those stack traces are all over the map, aren't they. Either you
> are hitting a dozen different Postgres bugs that no one else has ever
> seen, or you've got a flaky machine. I think the second is considerably
> more likely --- especially since several of the crashes are in startup
> code that every backend process ought to execute exactly the same way
> every time.
>
> Perhaps bad RAM, or a bad motherboard? I've also seen machines go nuts
> like this if the fan froze up, allowing the CPU to overheat. Anyway,
> take it back to Apple ... I hope it's still under warranty ...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings