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 2E60ED1B173 for ; Sat, 24 Jul 2004 16:40:55 -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 08536-01 for ; Sat, 24 Jul 2004 19:40:51 +0000 (GMT) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by svr1.postgresql.org (Postfix) with ESMTP id 7B76FD1B257 for ; Sat, 24 Jul 2004 16:40:48 -0300 (ADT) Received: from h-69-3-219-65.chcgilgm.dynamic.covad.net ([69.3.219.65] helo=[192.168.0.2]) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BoSO1-0004WJ-00 for pgsql-admin@postgresql.org; Sat, 24 Jul 2004 12:40:49 -0700 Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <59BCCE76-DDA9-11D8-AF0A-0050E490FE72@earthlink.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: pgsql-admin@postgresql.org From: Colin Stagner Subject: PG crashes MacOS 10.3.4 Date: Sat, 24 Jul 2004 14:40:43 -0500 X-Pgp-Agent: GPGMail 1.0.1 (v33, 10.3) X-Mailer: Apple Mail (2.618) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.9 tagged_above=0.0 required=5.0 tests=FROM_ENDS_IN_NUMS X-Spam-Level: X-Archive-Number: 200407/314 X-Sequence-Number: 14382 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am having some backend stability problems with postgresql 7.4.3 on MacOS 10.3.4 ($OSTYPE=darwin7.0). I compiled 7.4.3 from the source less than two weeks ago. 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. After the machine reboots, the exact same COPY FROM statement can be executed without incident. Nothing revealing is written to system.log, console.log, or the postgresql logfile in debug mode. I have confirmed it is the database server itself, and not the client (which in this case happens to be DBD::Pg), which is crashing by running the client on another machine. I have not changed any of the defaults in postgresql.conf. Any ideas? - -Colin Stagner -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFBArs/uq9VKK6yTRkRAo9RAJ0fIoZiPLiIDYO9H+j/IPBEJ2DF6wCdFvpo DUypd+v5j5ggcW0SWfOL2fY= =/Gm7 -----END PGP SIGNATURE-----