From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-performance@postgresql.org
To: delongboy <sdelong@saucontech.com>
Subject: Re: Increasing WAL usage followed by sudden drop
Date: Thu, 16 Aug 2012 11:39:40 -0500
Message-ID: <502CDBFC02000025000497B2@gw.wicourts.gov> (raw)
In-Reply-To: <1345134711660-5720136.post@n5.nabble.com>
References: <385621813.89890122.1344620116156.JavaMail.root@email>
<5029A543.4090503@agliodbs.com>
<1345134711660-5720136.post@n5.nabble.com>
delongboy <sdelong@saucontech.com> 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
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: Kevin.Grittner@wicourts.gov, sdelong@saucontech.com
Subject: Re: Increasing WAL usage followed by sudden drop
In-Reply-To: <502CDBFC02000025000497B2@gw.wicourts.gov>
* 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