Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 4C39E1337B43 for ; Wed, 16 Mar 2011 14:27:56 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 55183-02 for ; Wed, 16 Mar 2011 17:27:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from cpoproxy1-pub.bluehost.com (cpoproxy1-pub.bluehost.com [69.89.21.11]) by mail.postgresql.org (Postfix) with SMTP id 6CE4013364DE for ; Wed, 16 Mar 2011 14:27:48 -0300 (ADT) Received: (qmail 11922 invoked by uid 0); 16 Mar 2011 17:27:46 -0000 Received: from unknown (HELO host159.hostmonster.com) (74.220.207.159) by cpoproxy1.bluehost.com with SMTP; 16 Mar 2011 17:27:45 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=timbira.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=UVBWKTmncDv9oIIm3TyH5B1jkSAbdFToV5AF+D5f3rCsBidgLvxpUERzfWtxW8ZpgmTtYktpB9DEv6oT/xx4tofrVoOedRqJ+zJ0jSxm/RKBSoWn5xRfSBGdWpKkRkPp; Received: from 200-140-104-167.pmjce203.dial.brasiltelecom.net.br ([200.140.104.167]) by host159.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1PzuVc-0001aI-Rj; Wed, 16 Mar 2011 11:27:45 -0600 Message-ID: <4D80F308.3050207@timbira.com> Date: Wed, 16 Mar 2011 14:27:36 -0300 From: Euler Taveira de Oliveira User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20101227 Icedove/3.0.11 MIME-Version: 1.0 To: Tech Madhu CC: pgsql-performance@postgresql.org Subject: Re: pg_xlog size References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Identified-User: {1651:host159.hostmonster.com:timbirac:timbira.com} {sentby:smtp auth 200.140.104.167 authed with euler@timbira.com} X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201103/168 X-Sequence-Number: 42847 Em 15-03-2011 12:09, Tech Madhu escreveu: [This is not a performance question, next time post at the appropriate list, that is -general] > Everything works fine (w.r.t replication), but the pg_xlog size grows > continuously, though i had no operations going on. Also the archiving to > the other side filled up the other side FS. > ls -l /var/postgres/data/pg_xlog | wc -l > 103 Did you consider using pg_archivecleanup [1]? > At start, there were only 15 files. The max_wal_segments is 32, but not > sure why iam seeing 103 files. Also the archiving dir size doubled > (w.r.t number of files archived). and filled up the filesystem. > I manually logged into postgres and run checkpoint; did not see any file > reduction > max_wal_segments [2] is *not* related to archiving activity. [1] http://www.postgresql.org/docs/9.0/static/pgarchivecleanup.html [2] http://www.postgresql.org/docs/9.0/static/runtime-config-wal.html#GUC-WAL-KEEP-SEGMENTS -- Euler Taveira de Oliveira http://www.timbira.com/