aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/misc/postgresql.conf.sample
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2015-03-15 17:37:07 +0100
committerAndres Freund <andres@anarazel.de>2015-03-15 17:37:07 +0100
commita0f5954af19ddcfea946b15744f2006a789dc4bd (patch)
treef1804d6c5e464c1c22c1022dc7525b896fac1071 /src/backend/utils/misc/postgresql.conf.sample
parent241f088f3632814fe9dbd5bcbc509ec42a268d01 (diff)
downloadpostgresql-a0f5954af19ddcfea946b15744f2006a789dc4bd.tar.gz
postgresql-a0f5954af19ddcfea946b15744f2006a789dc4bd.zip
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.
Diffstat (limited to 'src/backend/utils/misc/postgresql.conf.sample')
-rw-r--r--src/backend/utils/misc/postgresql.conf.sample2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
index d7a61f1fc4b..110983f1764 100644
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -199,7 +199,7 @@
# - Checkpoints -
#checkpoint_timeout = 5min # range 30s-1h
-#max_wal_size = 128MB # in logfile segments
+#max_wal_size = 1GB
#min_wal_size = 80MB
#checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0
#checkpoint_warning = 30s # 0 disables