From 4b113d9cdc8654e3f979497e057c7f9062bfa612 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 5 Feb 2010 23:37:43 +0000 Subject: Document that archive_timeout will force new WAL files even if a single checkpoint has happened, and recommend adjusting checkpoint_timeout to reduce the impact of this. --- doc/src/sgml/config.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index d6c739d96b3..a5f520057e3 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ - + Server Configuration @@ -1739,7 +1739,11 @@ archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"' # Windows server to switch to a new WAL segment file periodically. When this parameter is greater than zero, the server will switch to a new segment file whenever this many seconds have elapsed since the last - segment file switch. Note that archived files that are closed early + segment file switch, and there has been any database activity, + including a single checkpoint. (Increasing + checkpoint_timeout will reduce unnecessary + checkpoints on an idle system.) + Note that archived files that are closed early due to a forced switch are still the same length as completely full files. Therefore, it is unwise to use a very short archive_timeout — it will bloat your archive -- cgit v1.2.3