From: Shaun Thomas <sthomas@peak6.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Using incrond for archiving
Date: Mon, 14 Nov 2011 15:58:18 -0600
Message-ID: <4EC18EFA.9070603@peak6.com> (raw)
In-Reply-To: <4EC137F40200002500042ECC@gw.wicourts.gov>
References: <4EBD9FDE.4000104@peak6.com>
<4EC1892F.2050506@peak6.com>
<4EC137F40200002500042ECC@gw.wicourts.gov>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sthomas@peak6.com, Kevin.Grittner@wicourts.gov
Subject: Re: Using incrond for archiving
In-Reply-To: <4EC18EFA.9070603@peak6.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox