|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.94 2006/11/05 22:42:07 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.95 2006/11/12 05:12:42 neilc Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter Id="runtime-config"> |
4 | 4 | <title>Server Configuration</title> |
@@ -1601,24 +1601,22 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows |
1601 | 1601 | </indexterm> |
1602 | 1602 | <listitem> |
1603 | 1603 | <para> |
1604 | | - The <xref linkend="guc-archive-command"> is only invoked on completed |
1605 | | - WAL segments. Hence, |
1606 | | - if your server generates only little WAL traffic (or has slack periods |
1607 | | - where it does so), there could be a long delay between the completion |
1608 | | - of a transaction and its safe recording in archive storage. To put |
1609 | | - a limit on how old unarchived data can be, you can set |
1610 | | - <varname>archive_timeout</> to force the server to switch |
1611 | | - to a new WAL segment file periodically. When this parameter is |
1612 | | - greater than zero, the server will switch to a new segment file |
1613 | | - whenever this many seconds elapse since the last segment file switch. |
1614 | | - Note that archived |
1615 | | - files that are closed early due to a forced switch are still the same |
1616 | | - length as completely full files. It is therefore unwise to set a very |
1617 | | - short <varname>archive_timeout</> — it will bloat your archive |
| 1604 | + The <xref linkend="guc-archive-command"> is only invoked on |
| 1605 | + completed WAL segments. Hence, if your server generates little WAL |
| 1606 | + traffic (or has slack periods where it does so), there could be a |
| 1607 | + long delay between the completion of a transaction and its safe |
| 1608 | + recording in archive storage. To put a limit on how old unarchived |
| 1609 | + data can be, you can set <varname>archive_timeout</> to force the |
| 1610 | + server to switch to a new WAL segment file periodically. When this |
| 1611 | + parameter is greater than zero, the server will switch to a new |
| 1612 | + segment file whenever this many seconds have elapsed since the last |
| 1613 | + segment file switch. Note that archived files that are closed early |
| 1614 | + due to a forced switch are still the same length as completely full |
| 1615 | + files. Therefore, it is unwise to use a very short |
| 1616 | + <varname>archive_timeout</> — it will bloat your archive |
1618 | 1617 | storage. <varname>archive_timeout</> settings of a minute or so are |
1619 | | - usually reasonable. |
1620 | | - This parameter can only be set in the <filename>postgresql.conf</> |
1621 | | - file or on the server command line. |
| 1618 | + usually reasonable. This parameter can only be set in the |
| 1619 | + <filename>postgresql.conf</> file or on the server command line. |
1622 | 1620 | </para> |
1623 | 1621 | </listitem> |
1624 | 1622 | </varlistentry> |
|
