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

Commit17ddb7d

Browse files
committed
Fix documentation reference to maximum allowed for autovacuum_freeze_max_age.
The documentation mentioned setting autovacuum_freeze_max_age to"its maximum allowed value of a little less than two billion".This led to a post asking about the exact maximum allowed value,which is precisely two billion, not "a little less".Based on question by Radovan Jablonovsky. Backpatch to 8.3.
1 parent3d3218a commit17ddb7d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/maintenance.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -450,8 +450,8 @@
450450
will take more space, because it must store the commit status of all
451451
transactions back to the <varname>autovacuum_freeze_max_age</> horizon.
452452
The commit status uses two bits per transaction, so if
453-
<varname>autovacuum_freeze_max_age</> is set to its maximum allowed value of
454-
a little less than two billion, <filename>pg_clog</> can be expected to
453+
<varname>autovacuum_freeze_max_age</> is set to its maximum allowed
454+
value of two billion, <filename>pg_clog</> can be expected to
455455
grow to about half a gigabyte. If this is trivial compared to your
456456
total database size, setting <varname>autovacuum_freeze_max_age</> to
457457
its maximum allowed value is recommended. Otherwise, set it depending

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp