Date: Thu, 23 Aug 2012 07:43:18 -0700 (PDT)
From: delongboy <sdelong@saucontech.com>
To: pgsql-performance@postgresql.org
Message-ID: <1345732998244-5720953.post@n5.nabble.com>
In-Reply-To: 
 <CAMkU=1yPTF7YQnn=kWepoX3=9GB3D5N8Jz3Fe6gfd-YF1XCafg@mail.gmail.com>
References: <385621813.89890122.1344620116156.JavaMail.root@email>
	<5029A543.4090503@agliodbs.com>
	<1345134711660-5720136.post@n5.nabble.com>
	<801082735.54549.1345215661255.JavaMail.root@agliodbs.com>
	<1345226019192-5720250.post@n5.nabble.com>
	<CAMkU=1xo=o8+wA5Pa=P18OcdBwKx0J=0PCy+HBUDVPsazX3i4Q@mail.gmail.com>
	<1345495869310-5720492.post@n5.nabble.com>
	<CAMkU=1yPTF7YQnn=kWepoX3=9GB3D5N8Jz3Fe6gfd-YF1XCafg@mail.gmail.com>
Subject: Re: Increasing WAL usage followed by sudden drop
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Jeff Janes wrote
> 
> It seems like it shouldn't be all that hard to write a tool to parse
> WAL logs in a context-free basis (i.e. without the backup to start
> applying them to) and emit some kind of descriptions of the records
> and their sizes.  But I don't know about such a tool already existing,
> and am not able to offer to create one.  (And assuming one existed,
> keeping it in sync with the main code would be a continuing problem)
> 

I appreciate your help Jeff.  I have come across what would seem such a
tool.
Its called xlogdump
I am working on getting it installed, having issues with libs I think at the
moment. I will let you know how it works out.

Thank you everybody for your input!


--
View this message in context: http://postgresql.1045698.n5.nabble.com/Increasing-WAL-usage-followed-by-sudden-drop-tp5719567p5720953.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.