Re: Total crash of my db-server - Mailing list pgsql-general

hi tom,

ok, I understand this.

But: There is ONLY postgres running on this particular
machine. And it's mostly when backup (dumpall) and/or
vacuuming/reindexing is going on.

In my opinion, postgresql does something on my machine
that leads to these complete system lockups.


--

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)
--------------------------------------------------------
Ihr SMS-Gateway: JETZT NEU unter: http://sms.city-map.de
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: "Ian Barwick" <barwick@gmx.net>
Cc: "Henrik Steffen" <steffen@city-map.de>; <pgsql-general@postgresql.org>;
"Justin Clift" <justin@postgresql.org>
Sent: Sunday, December 15, 2002 5:29 PM
Subject: Re: [GENERAL] Total crash of my db-server


> >> 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