From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Reduce checkpoints and WAL traffic on low activity database serv |
Date: | 2011-11-02 16:15:57 |
Message-ID: | CA+TgmoYc3u6+1kBH5Z8xDFA-S-wT7xrjGmUi1+rfQv=Xq8ptfQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Wed, Nov 2, 2011 at 11:39 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Reduce checkpoints and WAL traffic on low activity database server
> Previously, we skipped a checkpoint if no WAL had been written since
> last checkpoint, though this does not appear in user documentation.
> As of now, we skip a checkpoint until we have written at least one
> enough WAL to switch the next WAL file. This greatly reduces the
> level of activity and number of WAL messages generated by a very
> low activity server. This is safe because the purpose of a checkpoint
> is to act as a starting place for a recovery, in case of crash.
> This patch maintains minimal WAL volume for replay in case of crash,
> thus maintaining very low crash recovery time.
I think you need to update the docs, for checkpoint_timeout if nothing else.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-11-02 16:34:11 | Re: pgsql: Reduce checkpoints and WAL traffic on low activity database serv |
Previous Message | Simon Riggs | 2011-11-02 15:39:07 | pgsql: Reduce checkpoints and WAL traffic on low activity database serv |
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2011-11-02 16:25:00 | Re: DeArchiver process |
Previous Message | Robert Haas | 2011-11-02 16:14:04 | Re: DeArchiver process |