Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T236v-0001Ra-IK for pgsql-performance@postgresql.org; Thu, 16 Aug 2012 16:39:53 +0000 Received: from gwmta.wicourts.gov ([165.219.244.99] helo=gw.wicourts.gov) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T236t-0003MH-N2 for pgsql-performance@postgresql.org; Thu, 16 Aug 2012 16:39:53 +0000 Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Thu, 16 Aug 2012 11:39:51 -0500 Message-Id: <502CDBFC02000025000497B2@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.2 Date: Thu, 16 Aug 2012 11:39:40 -0500 From: "Kevin Grittner" To: , "delongboy" Subject: Re: Increasing WAL usage followed by sudden drop References: <385621813.89890122.1344620116156.JavaMail.root@email> <5029A543.4090503@agliodbs.com> <1345134711660-5720136.post@n5.nabble.com> In-Reply-To: <1345134711660-5720136.post@n5.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201208/110 X-Sequence-Number: 47648 delongboy 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. Maybe autovacuum freezing tuples (which is a WAL-logged operation) as tables periodically hit the autovacuum_freeze_max_age limit? -Kevin