Date: Fri, 17 Aug 2012 10:53:39 -0700 (PDT)
From: delongboy <sdelong@saucontech.com>
To: pgsql-performance@postgresql.org
Message-ID: <1345226019192-5720250.post@n5.nabble.com>
In-Reply-To: <801082735.54549.1345215661255.JavaMail.root@agliodbs.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>
Subject: Re: Increasing WAL usage followed by sudden drop
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Josh Berkus wrote
> 
>> We are not doing anything to postgres that would cause the rise and
>> drop.
>> Data base activity is pretty consistent.  nor are we doing any kind
>> of
>> purge.  This week the drop occurred after 6 days.  We are thinking it
>> must
>> be some kind of internal postgres activity but we can't track it
>> down.
> 
> Well, we certainly can't figure it out on this list by blind guessing ...
> 

Have to agree with you there.  Unfortunately this is where we've ended up.
What can we look at and/or show that would help us to narrow it down?  Is
there anyway we can look into the wal file and see exactly what is being
sent?  I think this might actually give us the most insight.


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