Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T22zF-0007Rz-6q for pgsql-performance@postgresql.org; Thu, 16 Aug 2012 16:31:57 +0000 Received: from sam.nabble.com ([216.139.236.26]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T22zA-0002ZR-A4 for pgsql-performance@postgresql.org; Thu, 16 Aug 2012 16:31:56 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T22z9-0003bv-Lb for pgsql-performance@postgresql.org; Thu, 16 Aug 2012 09:31:51 -0700 Date: Thu, 16 Aug 2012 09:31:51 -0700 (PDT) From: delongboy To: pgsql-performance@postgresql.org Message-ID: <1345134711660-5720136.post@n5.nabble.com> In-Reply-To: <5029A543.4090503@agliodbs.com> References: <385621813.89890122.1344620116156.JavaMail.root@email> <5029A543.4090503@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 X-Pg-Spam-Score: -0.1 (/) X-Archive-Number: 201208/109 X-Sequence-Number: 47647 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. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Increasing-WAL-usage-followed-by-sudden-drop-tp5719567p5720136.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.