Date: Mon, 20 Aug 2012 13:51:09 -0700 (PDT)
From: delongboy <sdelong@saucontech.com>
To: pgsql-performance@postgresql.org
Message-ID: <1345495869310-5720492.post@n5.nabble.com>
In-Reply-To: 
 <CAMkU=1xo=o8+wA5Pa=P18OcdBwKx0J=0PCy+HBUDVPsazX3i4Q@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>
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
> 
> Maybe there is an easier way, but one thing would be to compile a test
> server (of the same version as the production) with WAL_DEBUG defined
> in src/include/pg_config_manual.h, turn on the wal_debug guc, and
> crank up trace_recovery_messages.  Then replay the WAL log files from
> production through this test server and see what it logs.  That
> requires that you have
> 
> Easier would to be turn on wal_debug and watch the server log as the
> WAL logs are generated, instead of recovered, but you probably don't
> want to do that on production.  So you would need a workload generator
> that also exhibits the phenomenon of interest.
> 

This sounds like it may help me see what is going on.  However I am not
finding very much documentation as to how to do this exactly.  What I have
is it seems this has to be set and postgres needs to be re-compiled to
enable it.  Is this true?  As that would not really be a viable option right
now.  I am in position to set up a test server and run wal files through it. 
But I am not sure how to accomplish this exactly?  Is there somewhere you
anyone could point me to find documentation on how to do this?

Thanks a lot for everyone's input so far.


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