|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.249 2010/02/03 17:25:05 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.250 2010/02/05 23:37:43 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter Id="runtime-config">
|
4 | 4 | <title>Server Configuration</title>
|
@@ -1739,7 +1739,11 @@ archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"' # Windows
|
1739 | 1739 | server to switch to a new WAL segment file periodically. When this
|
1740 | 1740 | parameter is greater than zero, the server will switch to a new
|
1741 | 1741 | segment file whenever this many seconds have elapsed since the last
|
1742 |
| - segment file switch. Note that archived files that are closed early |
| 1742 | + segment file switch, and there has been any database activity, |
| 1743 | + including a single checkpoint. (Increasing |
| 1744 | + <varname>checkpoint_timeout</> will reduce unnecessary |
| 1745 | + checkpoints on an idle system.) |
| 1746 | + Note that archived files that are closed early |
1743 | 1747 | due to a forced switch are still the same length as completely full
|
1744 | 1748 | files. Therefore, it is unwise to use a very short
|
1745 | 1749 | <varname>archive_timeout</> — it will bloat your archive
|
|