Marc Simonin <m.simonin@allibert-trekking.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
