From: Florian Weimer <fweimer@bfk.de>
To: pgsql-performance@postgresql.org
Subject: Wrong docs on checkpoint_segments?
Date: Fri, 07 Jan 2011 12:45:25 +0000
Message-ID: <82aajcg9wa.fsf@mid.bfk.de> (raw)
On 9.0, this configuration
checkpoint_segments = 512 # in logfile segments, min 1, 16MB each
results in 1034 segments, so the effective logfile segment size is 32 MB.
The documentation says this:
Maximum number of log file segments between automatic WAL
checkpoints (each segment is normally 16 megabytes). The default
is three segments. Increasing this parameter can increase the
amount of time needed for crash recovery. This parameter can only
be set in the postgresql.conf file or on the server command line.
It would probably make sense to change this to
checkpoint_segments = 3 # each one effectively needs about 32MB on disk
and:
Number of log file segments between automatic WAL checkpoints. The
default is three segments. Increasing this parameter can increase
the amount of time needed for crash recovery. This parameter can
only be set in the postgresql.conf file or on the server command
line.
Each segment normally requires 16 megabytes on disk. Segments can
only be recycled after a checkpoint has completed, so disk space
is required for twice the number of configured segments, plus some
reserve.
Perhaps it would also make sense to mention that increasing the
segment count decreases WAL traffic, and that changing this value does
not have an impact on transaction sizes?
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: fweimer@bfk.de
Subject: Re: Wrong docs on checkpoint_segments?
In-Reply-To: <82aajcg9wa.fsf@mid.bfk.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox