rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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:
Tom Lane 2006-09-03 19:06:15 +00:00
parent 8fad2e3ff4
commit 7781916ab5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/config.sgml
View File

@ -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">
<title>Server Configuration</title>
@ -1591,8 +1591,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
</indexterm>
<listitem>
<para>
By default, the <xref linkend="guc-archive-command"> is only invoked
on completed WAL segments. Hence,
The <xref linkend="guc-archive-command"> is only invoked on completed
WAL segments. Hence,
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
of a transaction and its safe recording in archive storage. To put