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

Commit078d471

Browse files
committed
Lower *_freeze_max_age minimum values.
The old minimum values are rather large, making it time consuming totest related behaviour. Additionally the current limits, especially formultixacts, can be problematic in space-constrained systems. 10000000multixacts can contain a lot of members.Since there's no good reason for the current limits, lower them a goodbit. Setting them to 0 would be a bad idea, triggering endless vacuums,so still retain a limit.While at it fix autovacuum_multixact_freeze_max_age to refer tomultixact.c instead of varsup.c.Reviewed-By: Robert HaasDiscussion: CA+TgmoYmQPHcrc3GSs7vwvrbTkbcGD9Gik=OztbDGGrovkkEzQ@mail.gmail.comBackpatch: 9.0 (in parts)
1 parentc69e7d5 commit078d471

File tree

1 file changed

+1
-1
lines changed
  • src/backend/utils/misc

1 file changed

+1
-1
lines changed

‎src/backend/utils/misc/guc.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1973,7 +1973,7 @@ static struct config_int ConfigureNamesInt[] =
19731973
},
19741974
&autovacuum_freeze_max_age,
19751975
/* see pg_resetxlog if you change the upper-limit value */
1976-
200000000,100000000,2000000000,NULL,NULL
1976+
200000000,100000,2000000000,NULL,NULL
19771977
},
19781978
{
19791979
/* see max_connections */

0 commit comments

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