pgsql: Revert "Reduce checkpoints and WAL traffic on low activity datab

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Revert "Reduce checkpoints and WAL traffic on low activity datab
Date: 2012-06-13 22:49:37
Message-ID: E1SewNd-0002Fw-0R@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revert "Reduce checkpoints and WAL traffic on low activity database server"

This reverts commit 18fb9d8d21a28caddb72c7ffbdd7b96d52ff9724. Per
discussion, it does not seem like a good idea to allow committed changes to
go un-checkpointed indefinitely, as could happen in a low-traffic server;
that makes us entirely reliant on the WAL stream with no redundancy that
might aid data recovery in case of disk failure.

This re-introduces the original problem of hot-standby setups generating a
small continuing stream of WAL traffic even when idle, but there are other
ways to address that without compromising crash recovery, so we'll revisit
that issue in a future release cycle.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/b8b69d89905e04b910bcd65efce1791477b45d35

Modified Files
--------------
src/backend/access/transam/xlog.c | 28 +++++++++++++---------------
1 files changed, 13 insertions(+), 15 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-06-13 22:57:39 pgsql: Remove release note entry for reverted patch.
Previous Message Tom Lane 2012-06-13 22:48:01 pgsql: Fix description of SQL-standard meaning of CREATE LOCAL TEMP TAB