Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 6ED779F9F47 for ; Fri, 22 Dec 2006 13:03:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 94583-02 for ; Fri, 22 Dec 2006 13:03:32 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 38B4A9F9DAD for ; Fri, 22 Dec 2006 13:03:33 -0400 (AST) thread-index: Accl6xz8R21E6/ZCQFCTpI5s1ztI8A== Received: from [192.168.0.22] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 Dec 2006 12:03:31 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 Content-Class: urn:content-classes:message Importance: normal Subject: Re: URGENT: Out of disk space pg_xlog From: "Simon Riggs" To: "Jeremy Haile" Cc: In-Reply-To: <1166806378.10592.281708161@webmail.messagingengine.com> References: <1166803606.2828.281701761@webmail.messagingengine.com> <1166806378.10592.281708161@webmail.messagingengine.com> Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 22 Dec 2006 17:02:43 +0000 Message-ID: <1166806963.3783.203.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Dec 2006 17:03:31.0234 (UTC) FILETIME=[1B812820:01C725EB] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/494 X-Sequence-Number: 22550 On Fri, 2006-12-22 at 11:52 -0500, Jeremy Haile wrote: > I would still appreciate ... explaining how to estimate size for a > pg_xlog partition. It seems like it can vary considerably depending on > how intensive your current transactions are. Is there a way to > determine a maximum? There should be at most 2*checkpoint_segments+1 files in pg_xlog, which are 16MB each. So you shouldn't be having a problem. If there are more than this, it could be because you have currently/previously had archive_command set and the archive command failed to execute correctly, or the database was shutdown/crashed prior to the archive commands being executed. IIRC there was a bug that allowed this to happen, but that was some time ago. Perhaps you could show us the dir listing, so we can check that there is not a new problem emerging? Can you also show us the contents of the pg_xlog/archive_status directory? Thanks. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com