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 9CC029FB24B for ; Tue, 29 Aug 2006 12:35:41 -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 12732-09 for ; Tue, 29 Aug 2006 12:35:32 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by postgresql.org (Postfix) with ESMTP id 8936D9FB24D for ; Tue, 29 Aug 2006 12:35:31 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id t13so2149931wxc for ; Tue, 29 Aug 2006 08:35:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=jVFpp3TI+5nkCGkQJ1LICJzAlmJ+lsl7jCM5cHXWOsTHoYY86VDTkVuSwgpm+i1sV4V3skTEgjkU3vYiTmodn/vJm/10sTZVcIPH5dpZYn/OPh2MItv3xLSjeyjL/HOaDbGp0uVPYvMWB6pjA77Fj1JYAILz6pbOpQHD1AKeSPw= Received: by 10.70.38.12 with SMTP id l12mr11654637wxl; Tue, 29 Aug 2006 08:35:31 -0700 (PDT) Received: by 10.70.73.10 with HTTP; Tue, 29 Aug 2006 08:35:30 -0700 (PDT) Message-ID: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com> Date: Tue, 29 Aug 2006 11:35:30 -0400 From: "Chris Hoover" To: "pgsql-admin@postgresql.org" Subject: Why so long between archive calls? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13781_16513133.1156865730932" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.059 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_00_10, HTML_MESSAGE, SPF_PASS X-Spam-Level: * X-Archive-Number: 200608/317 X-Sequence-Number: 22860 ------=_Part_13781_16513133.1156865730932 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_13781_16513133.1156865730932 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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
------=_Part_13781_16513133.1156865730932--