From 8ad8d916f99d19e0be7800992c828c3c1a01b693 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Sun, 25 Mar 2018 09:17:07 -0400 Subject: initdb: Further polishing of --wal-segsize option Extend documentation. Improve option parsing in case no argument was specified. --- doc/src/sgml/ref/initdb.sgml | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index 585665f1611..949b5a220f5 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -316,16 +316,22 @@ PostgreSQL documentation - + - Set the WAL segment size, in megabytes. This is - the size of each individual file in the WAL log. It may be useful - to adjust this size to control the granularity of WAL log shipping. - This option can only be set during initialization, and cannot be - changed later. - The default size is 16 megabytes. - The value must be a power of 2 between 1 and 1024 (megabytes). + Set the WAL segment size, in megabytes. This + is the size of each individual file in the WAL log. The default size + is 16 megabytes. The value must be a power of 2 between 1 and 1024 + (megabytes). This option can only be set during initialization, and + cannot be changed later. + + + + It may be useful to adjust this size to control the granularity of + WAL log shipping or archiving. Also, in databases with a high volume + of WAL, the sheer number of WAL files per directory can become a + performance and management problem. Increasing the WAL file size + will reduce the number of WAL files. -- cgit v1.2.3