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 7EA0DD72AA for ; Thu, 13 Oct 2005 14:18:28 -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 57353-06 for ; Thu, 13 Oct 2005 17:18:24 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 54A38D836B for ; Thu, 13 Oct 2005 14:18:24 -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 j9DHINKn023603; Thu, 13 Oct 2005 13:18:23 -0400 (EDT) To: "Nigel Bishop" Cc: pgsql-admin@postgresql.org Subject: Re: DB Cluster hanging In-reply-to: <72558D9A7573814BB4082A28843E03D401DA5548@intyodc01.uk.ioko365.com> References: <72558D9A7573814BB4082A28843E03D401DA5548@intyodc01.uk.ioko365.com> Comments: In-reply-to "Nigel Bishop" message dated "Thu, 13 Oct 2005 17:48:39 +0100" Date: Thu, 13 Oct 2005 13:18:23 -0400 Message-ID: <23602.1129223903@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/157 X-Sequence-Number: 19229 "Nigel Bishop" writes: > Hmm... a possible bug eh! I'll make sure that the log destination > doesn't fill again > This is what I have in the postgresql.conf file: > log_destination = 'stderr' > redirect_stderr = true I tried to reproduce the problem, without any success. What I did: * set up a small loopback filesystem, so I didn't have to actually fill my whole disk; * point Postgres logging into the loopback filesystem; * deliberately fill the filesystem. I didn't see any lockup. The syslogger subprocess started bleating on the original postmaster stderr: could not write to log file: No space left on device could not write to log file: No space left on device but it dropped the messages rather than hanging up, and the rest of the database sailed on just fine. When I freed up space on the loopback filesystem, logging resumed without any problem. So I dunno what went wrong for you. System-specific issue maybe? I tried this on Fedora Core 4 with CVS-tip Postgres (but the syslogger code hasn't changed materially since 8.0.2). Also, are you sure the postmaster is 8.0.3? There was an infinite-recursion-on-error bug in syslogger in 8.0 and 8.0.1. regards, tom lane