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

Re: [HACKERS] WAL archiving idle database

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jeff Davis" <pgsql(at)j-davis(dot)com>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>,"Brian Wipf" <brian(at)clickspace(dot)com>, <pgsql-general(at)postgresql(dot)org>,<pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [HACKERS] WAL archiving idle database
Date: 2007-10-29 17:17:09
Message-ID: 4725CF44.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
>>> On Mon, Oct 29, 2007 at 11:50 AM, in message
<1193676615(dot)7624(dot)140(dot)camel(at)dogma(dot)ljc(dot)laika(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
wrote: 

> Also, did you publish your pg_clearxlogtail program anywhere? I think
> that would be helpful to many people, but I don't see it on pgfoundry.
 
So far I've just included with the email on the hackers list.  I
have made one fix since: I found that an explicit close of stdout
speeds the worst-case situation to break-even.  (I'm guessing that's
safer, too.)  So in all of my tests it is now as fast or faster to
pipe through this on the way to gzip than to just pipe through gzip.
 
I'll see about getting that onto pgfoundry soon.
 
-Kevin



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-10-29 18:20:02
Subject: Re: [HACKERS] WAL archiving idle database
Previous:From: Peter EisentrautDate: 2007-10-29 16:54:00
Subject: Re: pg_ctl configurable timeout

pgsql-general by date

Next:From: Tom LaneDate: 2007-10-29 18:20:02
Subject: Re: [HACKERS] WAL archiving idle database
Previous:From: Richard HuxtonDate: 2007-10-29 17:14:52
Subject: Re: A few questions

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