Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit7781916

Browse files
committed
Fix non-improvement of description of archive_timeout. archive_command
is only invoked on completed WAL segments, period --- there's no 'bydefault' about it.
1 parent8fad2e3 commit7781916

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎doc/src/sgml/config.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.82 2006/09/02 23:12:16 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.83 2006/09/03 19:06:15 tgl Exp $ -->
22

33
<chapter Id="runtime-config">
44
<title>Server Configuration</title>
@@ -1591,8 +1591,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
15911591
</indexterm>
15921592
<listitem>
15931593
<para>
1594-
By default, the<xref linkend="guc-archive-command"> is only invoked
1595-
on completedWAL segments. Hence,
1594+
The<xref linkend="guc-archive-command"> is only invoked on completed
1595+
WAL segments. Hence,
15961596
if your server generates only little WAL traffic (or has slack periods
15971597
where it does so), there could be a long delay between the completion
15981598
of a transaction and its safe recording in archive storage. To put

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp