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

Re: Increasing WAL usage followed by sudden drop

From: delongboy <sdelong(at)saucontech(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Increasing WAL usage followed by sudden drop
Date: 2012-08-17 17:53:39
Message-ID: 1345226019192-5720250.post@n5.nabble.com (view raw or flat)
Thread:
Lists: pgsql-performance
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.


In response to

Responses

pgsql-performance by date

Next:From: Jeff JanesDate: 2012-08-17 18:42:27
Subject: Re: Increasing WAL usage followed by sudden drop
Previous:From: Joshua BerkusDate: 2012-08-17 15:01:01
Subject: Re: Increasing WAL usage followed by sudden drop

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