8000 Lower *_freeze_max_age minimum values. · postgres/postgres@020235a · GitHub
[go: up one dir, main page]
Skip to content

Commit 020235a

Browse files
anarazelanarazel
committed
Lower *_freeze_max_age minimum values.
The old minimum values are rather large, making it time consuming to test related behaviour. Additionally the current limits, especially for multixacts, can be problematic in space-constrained systems. 10000000 multixacts can contain a lot of members. Since there's no good reason for the current limits, lower them a good bit. 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 to multixact.c instead of varsup.c. Reviewed-By: Robert Haas Discussion: CA+TgmoYmQPHcrc3GSs7vwvrbTkbcGD9Gik=OztbDGGrovkkEzQ@mail.gmail.com Backpatch: back to 9.0 (in parts)
1 parent 82e1ba7 commit 020235a

File tree

1 file changed

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

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2510,17 +2510,17 @@ static struct config_int ConfigureNamesInt[] =
25102510
},
25112511
&autovacuum_freeze_max_age,
25122512
/* see pg_resetxlog if you change the upper-limit value */
2513-
200000000, 100000000, 2000000000,
2513+
200000000, 100000, 2000000000,
25142514
NULL, NULL, NULL
25152515
},
25162516
{
2517-
/* see varsup.c for why this is PGC_POSTMASTER not PGC_SIGHUP */
2517+
/* see multixact.c for why this is PGC_POSTMASTER not PGC_SIGHUP */
25182518
{"autovacuum_multixact_freeze_max_age", PGC_POSTMASTER, AUTOVACUUM,
25192519
gettext_noop("Multixact age at which to autovacuum a table to prevent multixact wraparound."),
25202520
NULL
25212521
},
25222522
&autovacuum_multixact_freeze_max_age,
2523-
400000000, 10000000, 2000000000,
2523+
400000000, 10000, 2000000000,
25242524
NULL, NULL, NULL
25252525
},
25262526
{

0 commit comments

Comments
 (0)
0