mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-30 21:21:16 +02:00
Fix non-improvement of description of archive_timeout. archive_command
is only invoked on completed WAL segments, period --- there's no 'by default' about it.
This commit is contained in:
parent
8fad2e3ff4
commit
7781916ab5
@ -1,4 +1,4 @@
|
|||||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.82 2006/09/02 23:12:16 momjian Exp $ -->
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.83 2006/09/03 19:06:15 tgl Exp $ -->
|
||||||
|
|
||||||
<chapter Id="runtime-config">
|
<chapter Id="runtime-config">
|
||||||
<title>Server Configuration</title>
|
<title>Server Configuration</title>
|
||||||
@ -1591,8 +1591,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
|
|||||||
</indexterm>
|
</indexterm>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
By default, the <xref linkend="guc-archive-command"> is only invoked
|
The <xref linkend="guc-archive-command"> is only invoked on completed
|
||||||
on completed WAL segments. Hence,
|
WAL segments. Hence,
|
||||||
if your server generates only little WAL traffic (or has slack periods
|
if your server generates only little WAL traffic (or has slack periods
|
||||||
where it does so), there could be a long delay between the completion
|
where it does so), there could be a long delay between the completion
|
||||||
of a transaction and its safe recording in archive storage. To put
|
of a transaction and its safe recording in archive storage. To put
|
||||||
|
Loading…
Reference in New Issue
Block a user