Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id CB1CF9F9DAD for ; Fri, 22 Dec 2006 13:37:33 -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 20800-08 for ; Fri, 22 Dec 2006 13:37:23 -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 828F09F9F7B for ; Fri, 22 Dec 2006 13:37:24 -0400 (AST) thread-index: Accl79ozomDMKAzWTiSLYRXhXVOiXg== 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:37:28 -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: <1166808625.17094.281711491@webmail.messagingengine.com> References: <1166803606.2828.281701761@webmail.messagingengine.com> <1166806378.10592.281708161@webmail.messagingengine.com> <1166806963.3783.203.camel@silverbirch.site> <1166808625.17094.281711491@webmail.messagingengine.com> Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 22 Dec 2006 17:36:39 +0000 Message-ID: <1166809000.3783.206.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Dec 2006 17:37:29.0109 (UTC) FILETIME=[DA2C3450:01C725EF] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/497 X-Sequence-Number: 22553 On Fri, 2006-12-22 at 12:30 -0500, Jeremy Haile wrote: > The archive_status directory is empty. I've never seen any files in > there and I've never set archive_command. > > Well, the problem has since resolved, but here is what is in the > directory now. Previously there were hundreds of files, but these > disappeared after Postgres performed the automatic recovery. What were you doing before the server crashed? Did you previously have checkpoint_segments set higher? When/how was it reduced? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com