pgsql: Increase max_wal_size's default from 128MB to 1GB. - Mailing list pgsql-committers

From Andres Freund
Subject pgsql: Increase max_wal_size's default from 128MB to 1GB.
Date
Msg-id E1YXBZ5-0006cI-AX@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/a0f5954af19ddcfea946b15744f2006a789dc4bd

Modified Files
--------------
doc/src/sgml/config.sgml                      |    2 +-
doc/src/sgml/wal.sgml                         |    2 +-
src/backend/access/transam/xlog.c             |    2 +-
src/backend/utils/misc/guc.c                  |    2 +-
src/backend/utils/misc/postgresql.conf.sample |    2 +-
5 files changed, 5 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pgsql: Invent PGC_SU_BACKEND and mark log_connections/log_disconnection
Next
From: Andres Freund
Date:
Subject: pgsql: Merge the various forms of transaction commit & abort records.