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 B538B9FB27B for ; Tue, 29 Aug 2006 13:35:59 -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 62878-01 for ; Tue, 29 Aug 2006 13:34:58 -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 9C1DB9FB284 for ; Tue, 29 Aug 2006 13:34:57 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id t13so2168333wxc for ; Tue, 29 Aug 2006 09:34:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=WcFUKvcxsEuVdbUA9M7JDqLFjwjjV8x3w6l/UWeBUDPlg6+JdgZSHNQdyM3pUkHxGFND5nsmgErG06+kqnpgvOMpxOL9tCTIiicv0UhAYzo5L2QQyT5oyumhmQaW/OyiXipfLm/iQ8eqJBMNxOO6gvfNElqx/HyPUL9qvnVaqNQ= Received: by 10.70.76.11 with SMTP id y11mr11685215wxa; Tue, 29 Aug 2006 09:34:56 -0700 (PDT) Received: by 10.70.73.10 with HTTP; Tue, 29 Aug 2006 09:34:56 -0700 (PDT) Message-ID: <1d219a6f0608290934g6d3ed785oa2814dbf3619306b@mail.gmail.com> Date: Tue, 29 Aug 2006 12:34:56 -0400 From: "Chris Hoover" To: andy.shellam-lists@mailnetwork.co.uk Subject: Re: Why so long between archive calls? Cc: pgsql-admin@postgresql.org In-Reply-To: <44F4690D.2010503@mailnetwork.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15315_12992624.1156869296420" References: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com> <44F4690D.2010503@mailnetwork.co.uk> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.614 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/322 X-Sequence-Number: 22865 ------=_Part_15315_12992624.1156869296420 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline The oldest log file that is not archived is: -rw------- 1 postgres postgres 16777216 Aug 28 15:24 00000001000001930000005A The command I am using is running successfully and I am getting good entries in my log files. ,15282,,2006-08-29 11:07:04.443 EDT,,13552,,,,LOG: archived transaction log file "00000001000001930000004E" ,15282,,2006-08-29 11:22:54.982 EDT,,13553,,,,LOG: archived transaction log file "00000001000001930000004F" ,15282,,2006-08-29 11:24:40.126 EDT,,13554,,,,LOG: archived transaction log file "000000010000019300000050" ,15282,,2006-08-29 11:32:04.650 EDT,,13555,,,,LOG: archived transaction log file "000000010000019300000051" ,15282,,2006-08-29 11:33:30.900 EDT,,13556,,,,LOG: archived transaction log file "000000010000019300000052" ,15282,,2006-08-29 11:37:21.333 EDT,,13557,,,,LOG: archived transaction log file "000000010000019300000053" ,15282,,2006-08-29 11:44:50.792 EDT,,13558,,,,LOG: archived transaction log file "000000010000019300000054" ,15282,,2006-08-29 12:24:54.566 EDT,,13559,,,,LOG: archived transaction log file "000000010000019300000055" ,15282,,2006-08-29 12:25:08.530 EDT,,13560,,,,LOG: archived transaction log file "000000010000019300000056" ,15282,,2006-08-29 12:25:10.754 EDT,,13561,,,,LOG: archived transaction log file "000000010000019300000057" ,15282,,2006-08-29 12:25:14.619 EDT,,13562,,,,LOG: archived transaction log file "000000010000019300000058" So, it looks like everything is good, just the archive command is not getting called enough. Thanks, Chris On 8/29/06, Andy Shellam wrote: > > 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! > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > ------=_Part_15315_12992624.1156869296420 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline The oldest log file that is not archived is:
-rw-------  1 postgres postgres 16777216 Aug 28 15:24 00000001000001930000005A

The command I am using is running successfully and I am getting good entries in my log files.
,15282,,2006-08-29 11:07:04.443 EDT,,13552,,,,LOG:  archived transaction log file "00000001000001930000004E"
,15282,,2006-08-29 11:22:54.982 EDT,,13553,,,,LOG:  archived transaction log file "00000001000001930000004F"
,15282,,2006-08-29 11:24:40.126 EDT,,13554,,,,LOG:  archived transaction log file "000000010000019300000050"
,15282,,2006-08-29 11:32:04.650 EDT,,13555,,,,LOG:  archived transaction log file "000000010000019300000051"
,15282,,2006-08-29 11:33:30.900 EDT,,13556,,,,LOG:  archived transaction log file "000000010000019300000052"
,15282,,2006-08-29 11:37:21.333 EDT,,13557,,,,LOG:  archived transaction log file "000000010000019300000053"
,15282,,2006-08-29 11:44:50.792 EDT,,13558,,,,LOG:  archived transaction log file "000000010000019300000054"
,15282,,2006-08-29 12:24:54.566 EDT,,13559,,,,LOG:  archived transaction log file "000000010000019300000055"
,15282,,2006-08-29 12:25:08.530 EDT,,13560,,,,LOG:  archived transaction log file "000000010000019300000056"
,15282,,2006-08-29 12:25:10.754 EDT,,13561,,,,LOG:  archived transaction log file "000000010000019300000057"
,15282,,2006-08-29 12:25:14.619 EDT,,13562,,,,LOG:  archived transaction log file "000000010000019300000058"

So, it looks like everything is good, just the archive command is not getting called enough.

Thanks,

Chris

On 8/29/06, Andy Shellam <andy.shellam-lists@mailnetwork.co.uk > wrote:
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!


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

------=_Part_15315_12992624.1156869296420--