diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/backup.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/installation.sgml | 14 | ||||
| -rw-r--r-- | doc/src/sgml/ref/initdb.sgml | 15 | ||||
| -rw-r--r-- | doc/src/sgml/wal.sgml | 13 |
4 files changed, 22 insertions, 22 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 95aeb35507e..bd55e8bb775 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -562,7 +562,7 @@ tar -cf backup.tar /usr/local/pgsql/data produces an indefinitely long sequence of WAL records. The system physically divides this sequence into WAL <firstterm>segment files</>, which are normally 16MB apiece (although the segment size - can be altered when building <productname>PostgreSQL</>). The segment + can be altered during <application>initdb</>). The segment files are given numeric names that reflect their position in the abstract WAL sequence. When not using WAL archiving, the system normally creates just a few segment files and then diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml index b178d3074bb..a1bae951457 100644 --- a/doc/src/sgml/installation.sgml +++ b/doc/src/sgml/installation.sgml @@ -1059,20 +1059,6 @@ su - postgres </varlistentry> <varlistentry> - <term><option>--with-wal-segsize=<replaceable>SEGSIZE</replaceable></option></term> - <listitem> - <para> - Set the <firstterm>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. - The default size is 16 megabytes. - The value must be a power of 2 between 1 and 1024 (megabytes). - Note that changing this value requires an initdb. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>--with-wal-blocksize=<replaceable>BLOCKSIZE</replaceable></option></term> <listitem> <para> diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index 6efb2e442d5..732fecab8ec 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -316,6 +316,21 @@ PostgreSQL documentation </varlistentry> <varlistentry> + <term><option>--wal-segsize=<replaceable>SEGSIZE</replaceable></option></term> + <listitem> + <para> + Set the <firstterm>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). + </para> + </listitem> + </varlistentry> + + <varlistentry> <term><option>-X <replaceable class="parameter">directory</replaceable></option></term> <term><option>--waldir=<replaceable class="parameter">directory</replaceable></option></term> <listitem> diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 940c37b21a3..ddcef5fbf53 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -752,13 +752,12 @@ <acronym>WAL</acronym> logs are stored in the directory <filename>pg_wal</filename> under the data directory, as a set of segment files, normally each 16 MB in size (but the size can be changed - by altering the <option>--with-wal-segsize</> configure option when - building the server). Each segment is divided into pages, normally - 8 kB each (this size can be changed via the <option>--with-wal-blocksize</> - configure option). The log record headers are described in - <filename>access/xlogrecord.h</filename>; the record content is dependent - on the type of event that is being logged. Segment files are given - ever-increasing numbers as names, starting at + by altering the <option>--wal-segsize</> initdb option). Each segment is + divided into pages, normally 8 kB each (this size can be changed via the + <option>--with-wal-blocksize</> configure option). The log record headers + are described in <filename>access/xlogrecord.h</filename>; the record + content is dependent on the type of event that is being logged. Segment + files are given ever-increasing numbers as names, starting at <filename>000000010000000000000000</filename>. The numbers do not wrap, but it will take a very, very long time to exhaust the available stock of numbers. |