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 868A6D81D5 for ; Thu, 13 Oct 2005 13:31:12 -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 48184-03 for ; Thu, 13 Oct 2005 16:31:09 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id C516DD811C for ; Thu, 13 Oct 2005 13:31:09 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 13 Oct 2005 11:31:09 -0500 Subject: Re: DB Cluster hanging From: Scott Marlowe To: codeWarrior Cc: pgsql-admin@postgresql.org In-Reply-To: References: <7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1129221069.29961.199.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 13 Oct 2005 11:31:09 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 required=5 tests=[AWL=0.007] X-Spam-Level: X-Archive-Number: 200510/154 X-Sequence-Number: 19226 If you can't / won't / don't use syslog and want your logs rotated anyway, look at apache's log rotator. It works a charm, and rotates every night at midnight the way I use it. Quite simple to set up and very reliable. On Thu, 2005-10-13 at 10:48, codeWarrior wrote: > Are you possibly running logrotate on the postgreSQL server logs ? Logrotate > is usually set to signal (SIGHUP) the log owner (in this case -- postgreSQL) > after rotating the log file... > > You normally can't just delete the logfiles and expect postgreSQL to > continue wherever you left it... you normally need to pg_ctl reload or > pg_ctl restart after dinking with the log files... > > "Nigel Bishop" wrote in message > news:7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com... > > Hi, > > > > I'm hoping that someone will be able to answer this query: > > > > 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. > > > > Eventually I had to issue a kill -9 on the postmaster, set > > log_statement_stats to false and restarted the cluster, It recovered > > itself and the data load carried on. > > > > My question is, is this normal behaviour when the logfile destination > > fills up? There was nothing in the logfile being used at the time of > > the hang, just stats data. > > > > PG version 8.0.3 with archived WAL logs enabled > > > > O/S version RH ES4 with 2 CPUs & 2Gb RAM > > > > Thanks very much for any input. > > > > > > Regards, > > > > Nigel Bishop > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 6: explain analyze is your friend > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org