Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 5D713632843 for ; Thu, 11 Feb 2010 18:43:55 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 50060-10 for ; Thu, 11 Feb 2010 22:43:30 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp-int-m.obspm.fr (smtp-int-m.obspm.fr [145.238.187.15]) by mail.postgresql.org (Postfix) with ESMTP id 653CD632926 for ; Thu, 11 Feb 2010 18:43:44 -0400 (AST) Received: from obspm.fr (pcjas.obspm.fr [145.238.184.233]) by smtp-int-m.obspm.fr (8.14.3/8.14.3/SIO Observatoire de Paris - 07/2009) with ESMTP id o1BMhfAf025311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Feb 2010 23:43:42 +0100 Date: Thu, 11 Feb 2010 23:43:41 +0100 From: Albert Shih To: Kevin Grittner Cc: pgsql-admin@postgresql.org Subject: Re: pg_xlog Message-ID: <20100211224341.GB13434@obspm.fr> References: <20100211220907.GA13352@obspm.fr> <4B742E4A020000250002F1F4@gw.wicourts.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4B742E4A020000250002F1F4@gw.wicourts.gov> User-Agent: Mutt/1.5.20 (2009-06-14) X-Miltered: at smtp-int-m.obspm.fr with ID 4B74881D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4B74881D.000/145.238.184.233/pcjas.obspm.fr/obspm.fr/ X-j-chkmail-Score: MSGID : 4B74881D.000 on smtp-int-m.obspm.fr : j-chkmail score : . : R=. U=. O=. B=0.023 -> S=0.023 X-j-chkmail-Status: Ham X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=AWL=0.000, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/101 X-Sequence-Number: 33704 Le 11/02/2010 à 16:20:26-0600, Kevin Grittner a écrit > Albert Shih wrote: > > > How can I clean up the pg_xlog directory ? > > > > I've 710 go of those file. > > > > I've archive_mode on but not in the pg_xlog directory > > I've something like > > > > archive_mode = on # allows archiving to be done > > archive_command = 'cp -i %p /databases/Archives/WAL/%f > It will keep each WAL file until your archive command which is > supposed to copy it completes with an exit code of zero. It sounds > like that's not happening. What does that destination directory > look like? What messages are you seeing in your log files? > Thanks for the help In fact you right, they are some problem about the copy (wrong owner of the /WAL directory), so the WAL is not copied. That's why I got ... 45000 files in the pg_xlog. Thanks for your help. Regards. JAS -- Albert SHIH SIO batiment 15 Observatoire de Paris Meudon 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 Heure local/Local time: Jeu 11 fév 2010 23:42:11 CET