Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 0EE1F1FC706C for ; Mon, 14 Nov 2011 18:07:39 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 18894-01 for ; Mon, 14 Nov 2011 22:07:33 +0000 (UTC) X-Greylist: delayed 00:08:57.901746 by SQLgrey-1.8.0-rc2 Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id D36311FC7061 for ; Mon, 14 Nov 2011 18:07:32 -0400 (AST) Received: from smtp2.peak6.com ([38.98.137.9]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RQ4Xx-0006nK-13 for pgsql-performance@postgresql.org; Mon, 14 Nov 2011 21:58:34 +0000 X-AuditID: 0a02cb1e-b7c9dae000007b76-89-4ec18efd8035 Message-ID: <4EC18EFA.9070603@peak6.com> Date: Mon, 14 Nov 2011 15:58:18 -0600 From: Shaun Thomas Reply-To: Organization: Peak6 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Kevin Grittner CC: "pgsql-performance@postgresql.org" Subject: Re: Using incrond for archiving References: <4EBD9FDE.4000104@peak6.com> <4EC1892F.2050506@peak6.com> <4EC137F40200002500042ECC@gw.wicourts.gov> In-Reply-To: <4EC137F40200002500042ECC@gw.wicourts.gov> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed content-transfer-encoding: 7bit X-Originating-IP: [10.10.220.61] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNIsWRmVeSWpSXmKPExsXCxcQrpvuv76Cfwboki0fnl7NYXJ95jtmB yePCvmnsHq8mbGYJYIpqYLRJzMvLL0ksSVVISS1OtlUKcHX0NlNwySxOzknMzE0tUlLITLFV MlNSKMhJTE7NTc0rsVVKLChIzUtRsuNSwAA2QGWZeQqpecn5KZl56bZKnsH+uhYWppa6hkp2 8VhAQhNLxo3D95gLbrBX7Po3l6WBcTlbFyMnh4SAicTHv2ugbDGJC/fWg9m8AhoSx3+/Zeli 5OBgEVCVaLgvDRJmE1CTWLj7JiOILSQgK7F/1TlWEJtfQFhi34cmZhBbVCBE4tmE51BjBCVO znzCAmKLCBhI3FixAqyeWcBTouPUKrA5wgJGEg8+zWaDmFkg0XR5AhPIWk4Bc4kTnZ4Q5bYS F+ZcZ4Gw5SW2v53DDFEuJ3GnAWQVB9D1ChLXl/tPYBSahWTxLCTds5B0L2BkXsUoXlyWmJyR aVZQnFtSYKhXkJqYbaaXl1qyiREcsafldjCuuKB4iFGAg1GJh1ch/KCfEGtiWXFl7iFGCQ5m JRHeoDKgEG9KYmVValF+fFFpTmrxIUZTYIBNZJYSTc4HJpO8knhDY0NLU0tjMwMjE0sLJXHe r8+2+QkJpAPTQnZqakFqEUwfEwenVANj6ZVFFqKfBbdFaS9dvcpGR+/l3tQjrlMbTwS9ED9u Gve9Q64pPJ2Z2ZhTczJX8PmuFG2z/xViCTbv+fhvup8PeFH6upH7+v31ee3qRoVvv3+LzQhV fvm74lLQyp9frjMXxncecmUunL5u79Hzq89tXhsx7W091wVOBQH++YIfTrr/4uCP/pihxFKc kWioxVxUnAgA6+y9Hu4CAAA= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201111/169 X-Sequence-Number: 45680 On 11/14/2011 03:47 PM, Kevin Grittner wrote: > This sounds like it might be another manifestation of something that > confused me a while back: > > http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php > http://archives.postgresql.org/pgsql-hackers/2009-12/msg00060.php Interesting. That was probably the case for a couple of the older xlogs. I'm not sure what to think about the ones that were *not* deleted and still being "closed" occasionally. I'm just going to chalk it up to connection turnover, since it seems normal for multiple connections to have connections open to various transaction logs, even it they're not writing to them. I can handle the checks to pg_current_xlog_location so long as it's accurate. If pre-rotated transaction logs are still being written to, it's back to the drawing board for me. :) -- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604 312-676-8870 sthomas@peak6.com ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email