| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ian Barwick <barwick(at)gmx(dot)net> |
| Cc: | Henrik Steffen <steffen(at)city-map(dot)de>, pgsql-general(at)postgresql(dot)org, Justin Clift <justin(at)postgresql(dot)org> |
| Subject: | Re: Total crash of my db-server |
| Date: | 2002-12-15 16:29:58 |
| Message-ID: | 9977.1039969798@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>> This *really* sounds like you have a system wide problem, not just a
>> PostgreSQL problem.
>>
>> Can't imagine how moving to MySQL will help with that. ;-)
Actually, moving to MySQL will make it worse. We can say with
confidence that a system lockup is not Postgres' fault because Postgres
does not (and will not) run as root. I'm not sure whether MySQL *must*
be root, but that seems to be a pretty common way of setting it up ...
and when you do that, you can't entirely exclude it from consideration
when you're looking at problems that would require root privileges to
cause.
> Addtionally, have you considered the possibility of a hardware
> problem?
I tend to agree with Ian on that --- it sounds more like flaky hardware
than anything else. Time for memtest86 and some disk testing too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CSN | 2002-12-15 18:30:39 | OIDS |
| Previous Message | Ian Barwick | 2002-12-15 15:47:45 | Re: Total crash of my db-server |