X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 00C049FA606 for ; Thu, 22 Jun 2006 11:22:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 82192-07 for ; Thu, 22 Jun 2006 11:22:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id CD9AE9F9ED6 for ; Thu, 22 Jun 2006 11:22:22 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k5MEMGxc023664; Thu, 22 Jun 2006 10:22:16 -0400 (EDT) To: andy.shellam@mailnetwork.co.uk cc: "'Alvaro Herrera'" , pgsql-admin@postgresql.org Subject: Re: 2,2gb of pg_xlog ?? In-reply-to: References: Comments: In-reply-to "Andy Shellam" message dated "Thu, 22 Jun 2006 15:14:11 +0100" Date: Thu, 22 Jun 2006 10:22:16 -0400 Message-ID: <23663.1150986136@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/199 X-Sequence-Number: 22161 "Andy Shellam" writes: >> Don't do this. Postgres itself will remove the file after the >> archive_command has copied it elsewhere. > In my 8.1.3 install, it didn't - when I specified a cp command, it left the > files there. I had to define the command as "mv" to have them moved. If it left the files there, it had a reason to (probably, that it wanted to rename them for use as new WAL segments). It is NOT NOT NOT the job of the archive_command to do anything except copy the data somewhere else. Back to the OP's problem: failure to recycle WAL segments requires some active looking into, not mindless removal of files. The only explanations I can think of are that he's got the checkpoint interval settings at wacko values, or more likely something is preventing checkpoints from completing; if so, it's desperately important to find out what and fix it. Manual file removal is addressing a symptom not the problem. regards, tom lane