Skip site navigation (1) Skip section navigation (2)

Re: Using incrond for archiving

From: Shaun Thomas <sthomas(at)peak6(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Using incrond for archiving
Date: 2011-11-14 21:58:18
Message-ID: 4EC18EFA.9070603@peak6.com (view raw or flat)
Thread:
Lists: pgsql-performance
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(at)peak6(dot)com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

In response to

pgsql-performance by date

Next:From: Cody CaughlanDate: 2011-11-14 21:58:52
Subject: Re: Slow queries / commits, mis-configuration or hardware issues?
Previous:From: Kevin GrittnerDate: 2011-11-14 21:47:00
Subject: Re: Using incrond for archiving

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group