X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E607CD1E95D for ; Tue, 30 Mar 2004 04:33:40 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 52727-01 for ; Tue, 30 Mar 2004 00:33:38 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id DBFE6D1D8A5 for ; Tue, 30 Mar 2004 00:33:37 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2U4Xa7d026104; Mon, 29 Mar 2004 23:33:36 -0500 (EST) To: Andrew Biagioni Cc: pgsql-admin@postgresql.org Subject: Re: Spontaneous PostgreSQL Server Reboot? In-reply-to: <4068F16C.6050800@e-greek.net> References: <4068F16C.6050800@e-greek.net> Comments: In-reply-to Andrew Biagioni message dated "Mon, 29 Mar 2004 23:02:52 -0500" Date: Mon, 29 Mar 2004 23:33:35 -0500 Message-ID: <26103.1080621215@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/382 X-Sequence-Number: 12951 Andrew Biagioni writes: > On three different machines running the same PostgreSQL version (7.3.5) > on Linux and almost identical databases, I have been plagued by > occasional, unexplainable (to me) reboots of the computer. Postgres can *not* cause a system reboot; it's only an unprivileged user process. (but see *) You are dealing with either kernel bugs, hardware errors, or some other root-level process requesting a reboot. Even though it being three different machines would seem to rule out hardware issues, I'd not jump to that conclusion ... you might be having some kind of common-mode hardware failure. Two questions to ask here: * did you buy all the RAM from the same vendor? * is the power utility flaky where you live? (If you say "but I've got a UPS", how old are its batteries?) My money would be on a kernel bug though. Are you up2date on kernel patches? regards, tom lane (*) ObFinePrint: at least, PG can't directly trigger a reboot. One scenario to think about is flaky RAM in an address range that doesn't get used until the machine is under significant load --- since you say Postgres is the only significant load on the machine, it's entirely possible that triggering of a hardware failure is closely correlated to what Postgres is doing. Similar remarks apply to broken disk hardware.