X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2748CD1B56F for ; Thu, 29 Jul 2004 13:38:53 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47844-04 for ; Thu, 29 Jul 2004 16:38:44 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 914C0D1B762 for ; Thu, 29 Jul 2004 13:38:42 -0300 (ADT) 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 i6TGcQZl015121; Thu, 29 Jul 2004 12:38:26 -0400 (EDT) To: Colin Stagner Cc: pgsql-admin@postgresql.org Subject: Re: PG crashes MacOS 10.3.4 In-reply-to: <59BCCE76-DDA9-11D8-AF0A-0050E490FE72@earthlink.net> References: <59BCCE76-DDA9-11D8-AF0A-0050E490FE72@earthlink.net> Comments: In-reply-to Colin Stagner message dated "Sat, 24 Jul 2004 14:40:43 -0500" Date: Thu, 29 Jul 2004 12:38:26 -0400 Message-ID: <15120.1091119106@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.1 tagged_above=0.0 required=5.0 tests=MAILTO_TO_SPAM_ADDR X-Spam-Level: * X-Archive-Number: 200407/315 X-Sequence-Number: 14383 Colin Stagner writes: > At random intervals that seem to vary by database uptime and usage, a > COPY [table] FROM [file] statement involving maybe 20k - 80k rows > (larger amounts of data than I usually work with, but nothing the > server shouldn't be able to handle) will crash the machine. The screen > freezes, except for the mouse which freezes after about 30 seconds, and > the machine doesn't respond to keyboard or mouse input. Attempts to SSH > into the machine fail-- its not just the GUI locking up. The machine > must be cold-booted with the reset button. As an unprivileged process, Postgres *cannot* crash the machine --- at least not on sanely-written operating systems, and OS X qualifies. A system-wide lockup is either a hardware fault or a kernel bug. My money is on an intermittent hardware problem. regards, tom lane