From: delongboy <sdelong@saucontech.com>
To: pgsql-performance@postgresql.org
Subject: Re: Increasing WAL usage followed by sudden drop
Date: Mon, 20 Aug 2012 13:51:09 -0700 (PDT)
Message-ID: <1345495869310-5720492.post@n5.nabble.com> (raw)
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>
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-tp5719567p57204...
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
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: sdelong@saucontech.com
Subject: Re: Increasing WAL usage followed by sudden drop
In-Reply-To: <1345495869310-5720492.post@n5.nabble.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