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 71EC4D82C7 for ; Thu, 13 Oct 2005 13:06:57 -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 41507-05 for ; Thu, 13 Oct 2005 16:06:53 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 7A5C2D8268 for ; Thu, 13 Oct 2005 13:06:53 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j9DG6rH0042045 for ; Thu, 13 Oct 2005 16:06:53 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j9DFlxjb036604 for pgsql-admin@postgresql.org; Thu, 13 Oct 2005 15:47:59 GMT (envelope-from news) From: "codeWarrior" X-Newsgroups: pgsql.admin Subject: Re: DB Cluster hanging Date: Thu, 13 Oct 2005 08:48:36 -0700 Organization: Hub.Org Networking Services Lines: 49 Message-ID: References: <7e974e490510130822q3a853039n4c96991179deae5a@mail.gmail.com> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-RFC2646: Format=Flowed; Original To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=-0.273 required=5 tests=[ALL_TRUSTED=-2.82, AWL=0.283, FORGED_HOTMAIL_RCVD2=1.079, PRIORITY_NO_NAME=1.185] X-Spam-Level: X-Archive-Number: 200510/150 X-Sequence-Number: 19222 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 >