X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 0DDFB9FA5FB for ; Wed, 6 Sep 2006 17:54:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 50088-04 for ; Wed, 6 Sep 2006 20:54:49 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 4B5D79FA34A for ; Wed, 6 Sep 2006 17:54:33 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k86KsUTt024339; Wed, 6 Sep 2006 16:54:30 -0400 (EDT) To: "Chris Hoover" cc: "Alvaro Herrera" , pgsql-admin@postgresql.org Subject: Re: Why so long between archive calls? In-reply-to: <1d219a6f0609061313q5f94ab54l9e84211e8b43c8fd@mail.gmail.com> 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> <1d219a6f0609061313q5f94ab54l9e84211e8b43c8fd@mail.gmail.com> Comments: In-reply-to "Chris Hoover" message dated "Wed, 06 Sep 2006 16:13:21 -0400" Date: Wed, 06 Sep 2006 16:54:30 -0400 Message-ID: <24338.1157576070@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/54 X-Sequence-Number: 22968 "Chris Hoover" writes: > Currenty, there are no .ready files in the pg_xlog/archive_status file. Well, that explains why the archiver thinks it has nothing to do. > 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 Are you sure that's an unarchived file, and not a file waiting to be used later? What's the current WAL endpoint address? (pg_controldata would tell you ... but your trace showed 000000010000019700000078 being archived, which would suggest that this one is just waiting to be reused.) Have you got a particularly large checkpoint_segments setting? regards, tom lane