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 8F63B9FB3B4 for ; Wed, 6 Sep 2006 17:13:45 -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 76657-01-4 for ; Wed, 6 Sep 2006 17:13:41 -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 A28209FB3B5 for ; Wed, 6 Sep 2006 17:13:22 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id t13so2913537wxc for ; Wed, 06 Sep 2006 13:13:21 -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=KRGRvx4kNyx0GRQCVtgFyfnbTQsXh+hCtDmCHdxFLQkL4UgQHtBQy1gYLHr+rPiuACZS3kPZ6cTZEDakxRvszc5CTSnQct+zSeWMVDZw//yzAxI8DlmLlx/Nf8Fx9NU9vq4+c5gnF5qe6cnzkSzofSlMVHHb5WdmFnwuq2tcFrk= Received: by 10.70.118.4 with SMTP id q4mr10477240wxc; Wed, 06 Sep 2006 13:13:21 -0700 (PDT) Received: by 10.70.73.10 with HTTP; Wed, 6 Sep 2006 13:13:21 -0700 (PDT) Message-ID: <1d219a6f0609061313q5f94ab54l9e84211e8b43c8fd@mail.gmail.com> Date: Wed, 6 Sep 2006 16:13:21 -0400 From: "Chris Hoover" To: "Tom Lane" Subject: Re: Why so long between archive calls? Cc: "Alvaro Herrera" , pgsql-admin@postgresql.org In-Reply-To: <23808.1157572848@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_185218_31674687.1157573601239" References: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com> <1d219a6f0608290934g6d3ed785oa2814dbf3619306b@mail.gmail.com> <1d219a6f0608301212k699061d0ge52c953ecc5bddfa@mail.gmail.com> <24247.1157059093@sss.pgh.pa.us> <1d219a6f0609011230t2407cba5u53a5e536ad4fbc20@mail.gmail.com> <25848.1157153334@sss.pgh.pa.us> <20060902014010.GA14288@alvh.no-ip.org> <26777.1157161705@sss.pgh.pa.us> <1d219a6f0609051333t70e1207eife3d0ad7a55a2e07@mail.gmail.com> <23808.1157572848@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.828 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_30_40, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/53 X-Sequence-Number: 22967 ------=_Part_185218_31674687.1157573601239 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Currenty, there are no .ready files in the pg_xlog/archive_status file. Like I mentioned, the db server was stoped and restarted on 9/5 am, but the oldest unarchived log file is: -rw------- 1 postgres postgres 16M Sep 1 04:04 0000000100000197000000F1 I'm not sure what is going on, since the db was stopped and restarted, there should be no hanging transactions. I would have believed all of the archive files from before the reboot would have been archived by now. Let me know if I can provide you with further information. This is my development/non-production db server, so I do have a little bit of lattitude on what I do with it. Chris On 9/6/06, Tom Lane wrote: > > "Chris Hoover" writes: > > Right now, I have 510 log files waiting to be archived totaling 8GB. > > ... > > Why is the server so far behind? > > Good question. The trace shows the archiver scanning > pg_xlog/archive_status/ > and apparently not finding any .ready files. What do you see in that > directory? > > regards, tom lane > ------=_Part_185218_31674687.1157573601239 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Currenty, there are no .ready files in the pg_xlog/archive_status file.

Like I mentioned, the db server was stoped and restarted on 9/5 am, but the oldest unarchived log file is:
-rw-------  1 postgres postgres 16M Sep  1 04:04 0000000100000197000000F1

I'm not sure what is going on, since the db was stopped and restarted, there should be no hanging transactions.  I would have believed all of the archive files from before the reboot would have been archived by now.

Let me know if I can provide you with further information.  This is my development/non-production db server, so I do have a little bit of lattitude on what I do with it.

Chris


On 9/6/06, Tom Lane < tgl@sss.pgh.pa.us> wrote:
"Chris Hoover" < revoohc@gmail.com> writes:
> Right now, I have 510 log files waiting to be archived totaling 8GB.
> ...
> Why is the server so far behind?

Good question.  The trace shows the archiver scanning pg_xlog/archive_status/
and apparently not finding any .ready files.  What do you see in that
directory?

                        regards, tom lane

------=_Part_185218_31674687.1157573601239--