From a0f5954af19ddcfea946b15744f2006a789dc4bd Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Sun, 15 Mar 2015 17:37:07 +0100 Subject: Increase max_wal_size's default from 128MB to 1GB. The introduction of min_wal_size & max_wal_size in 88e982302684 makes it feasible to increase the default upper bound in checkpoint size. Previously raising the default would lead to a increased disk footprint, even if more segments weren't beneficial. The low default of checkpoint size is one of common performance problem users have thus increasing the default makes sense. Setups where the increase in maximum disk usage is a problem will very likely have to run with a modified configuration anyway. Discussion: 54F4EFB8.40202@agliodbs.com, CA+TgmoZEAgX5oMGJOHVj8L7XOkAe05Gnf45rP40m-K3FhZRVKg@mail.gmail.com Author: Josh Berkus, after a discussion involving lots of people. --- src/backend/utils/misc/guc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend/utils/misc/guc.c') diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c index 7196b0b2157..26275bda129 100644 --- a/src/backend/utils/misc/guc.c +++ b/src/backend/utils/misc/guc.c @@ -2191,7 +2191,7 @@ static struct config_int ConfigureNamesInt[] = GUC_UNIT_XSEGS }, &max_wal_size, - 8, 2, INT_MAX, + 64, 2, INT_MAX, NULL, assign_max_wal_size, NULL }, -- cgit v1.2.3