Hi,
On Mon, Dec 16, 2002 at 01:45:07PM +0100, Henrik Steffen wrote:
> 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.
May be the problem is related to the old sig11 problem:
http://www.bitwizard.nl/sig11/
Greetings,
-tb
> ----- 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
--
Thomas Beutin tb@laokoon.IN-Berlin.DE
Beam me up, Scotty. There is no intelligent live down in Redmond.
