X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AA5B1D825A for ; Thu, 13 Oct 2005 13:12:14 -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 39217-09 for ; Thu, 13 Oct 2005 16:12:10 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 155B1D813A for ; Thu, 13 Oct 2005 13:12:09 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j9DGC8hv023011; Thu, 13 Oct 2005 12:12:08 -0400 (EDT) To: Nigel Bishop Cc: pgsql-admin@postgresql.org Subject: Re: DB Cluster hanging In-reply-to: <7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com> References: <7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com> Comments: In-reply-to Nigel Bishop message dated "Thu, 13 Oct 2005 16:22:28 +0100" Date: Thu, 13 Oct 2005 12:12:08 -0400 Message-ID: <23010.1129219928@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200510/148 X-Sequence-Number: 19220 Nigel Bishop writes: > Last night at 3am our Postgresql DB cluster hung. At the time data > was being loaded. The parameter log_statement_stats in the > postgresql.conf file was set to true. This was churning out data into > the logfile which was switching every 10Mb. Eventually the partition > where the logfiles are written to filled up – fair enough – this had > been going on since about 5.30pm the previous evening and the logfiles > were being generated at the rate of 4/5 a minute. The partition was > cleared of old logs and I expected the DB to spring in to life, but no > it just sat there. I could not connect with psql or pg_ctl to > shutdown the cluster. How was the logging being done exactly? syslog? redirect_stderr? If redirect_stderr, this could well be a PG bug --- I kinda doubt anyone has tested that scenario. regards, tom lane