checkpoints. This is a soft limit; WAL size can exceed

<varname>max_wal_size</> under special circumstances, like

under heavy load, a failing <varname>archive_command</>, or a high

<varname>wal_keep_segments</> setting. The default is128 MB.

<varname>wal_keep_segments</> setting. The default is1 GB.

Increasing this parameter can increase the amount of time needed for

crash recovery.

This parameter can only be set in the <filename>postgresql.conf</>

linkend="guc-checkpoint-timeout"> seconds, or if

<xref linkend="guc-max-wal-size"> is about to be exceeded,

whichever comes first.

The default settings are 5 minutes and128 MB, respectively.

The default settings are 5 minutes and1 GB, respectively.

If no WAL has been written since the previous checkpoint, new checkpoints

will be skipped even if <varname>checkpoint_timeout</> has passed.

(If WAL archiving is being used and you want to put a lower limit on how

intmax_wal_size=8;/*128 MB */

intmax_wal_size=64;/*1 GB */

intmin_wal_size=5;/* 80 MB */

intwal_keep_segments=0;

intXLOGbuffers=-1;

},

&max_wal_size,

8,2,INT_MAX,

64,2,INT_MAX,

NULL,assign_max_wal_size,NULL

},

# - 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