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 D52279FB24D for ; Tue, 29 Aug 2006 13:17:49 -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 51265-06 for ; Tue, 29 Aug 2006 13:17:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sydney.mailnetwork.co.uk (server88-208-192-113.live-servers.net [88.208.192.113]) by postgresql.org (Postfix) with ESMTP id 30A289FB24B for ; Tue, 29 Aug 2006 13:17:37 -0300 (ADT) Received: from [213.146.143.243] (port=32493 helo=[172.16.208.165]) by sydney.mailnetwork.co.uk with esmtpa (Exim 4.60) (envelope-from ) id 1GI6HP-0000oM-QO for pgsql-admin@postgresql.org; Tue, 29 Aug 2006 17:17:35 +0100 Message-ID: <44F4690D.2010503@mailnetwork.co.uk> Date: Tue, 29 Aug 2006 17:19:25 +0100 From: Andy Shellam Reply-To: andy.shellam-lists@mailnetwork.co.uk Organization: The Mail Network User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Why so long between archive calls? References: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com> In-Reply-To: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.133 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/320 X-Sequence-Number: 22863 Chris, I take it you've checked that the archive_command is actually succeeding (check the postgresql log file.) Perhaps try running it manually with an early log file as the PostgreSQL user account? When you say you're 500 files behind, how old is the earliest log? Andy. Chris Hoover wrote: > I am working on getting my development system working with archive > logging so I can use the pitr features of Postgres. However, I am > finding that the actual archiving is not keeping up with the > generation of the logs. I am now over 500 wal archive files behind > (8+ GB). > > What controls how often the archive_command is called? > > The actual running of my archive script is taking 1-2 seconds, so I'm > not sure why we are so far behind. > > Thanks for any advise, > > Chris > > PG 8.1.3 > RH AS 4 > !DSPAM:37,44f45f03143293039237985!