From 5efbdd36f1584d5e6e3870a05dc5f53692b18df6 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Thu, 7 Jun 2018 23:36:04 -0400 Subject: [PATCH] doc: Move some new options into better positions on man pages --- doc/src/sgml/ref/initdb.sgml | 41 ++++++++++++++++---------------- doc/src/sgml/ref/pg_dump.sgml | 30 +++++++++++------------ doc/src/sgml/ref/pg_dumpall.sgml | 30 +++++++++++------------ 3 files changed, 50 insertions(+), 51 deletions(-) diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index feefd9a41e..4489b585c7 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -334,27 +334,6 @@ PostgreSQL documentation - - - - - 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. - - - - @@ -366,6 +345,26 @@ PostgreSQL documentation + + + + + 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. + + + diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 64ced9fe04..f402d46b0c 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -789,21 +789,6 @@ PostgreSQL documentation - - - - - Do not wait forever to acquire shared table locks at the beginning of - the dump. Instead fail if unable to lock a table within the specified - timeout. The timeout may be - specified in any of the formats accepted by SET - statement_timeout. (Allowed formats vary depending on the server - version you are dumping from, but an integer number of milliseconds - is accepted by all versions.) - - - - @@ -819,6 +804,21 @@ PostgreSQL documentation + + + + + Do not wait forever to acquire shared table locks at the beginning of + the dump. Instead fail if unable to lock a table within the specified + timeout. The timeout may be + specified in any of the formats accepted by SET + statement_timeout. (Allowed formats vary depending on the server + version you are dumping from, but an integer number of milliseconds + is accepted by all versions.) + + + + diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index 8e5e7f9ef8..22cb790703 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -326,6 +326,21 @@ PostgreSQL documentation + + + + + When dumping a COPY or INSERT statement for a partitioned table, + target the root of the partitioning hierarchy which contains it rather + than the partition itself. This may be useful when reloading data on + a server where rows do not always fall into the same partitions as + they did on the original server. This could happen, for example, if + the partitioning column is of type text and the two system have + different definitions of the collation used to partition the data. + + + + @@ -342,21 +357,6 @@ PostgreSQL documentation - - - - - When dumping a COPY or INSERT statement for a partitioned table, - target the root of the partitioning hierarchy which contains it rather - than the partition itself. This may be useful when reloading data on - a server where rows do not always fall into the same partitions as - they did on the original server. This could happen, for example, if - the partitioning column is of type text and the two system have - different definitions of the collation used to partition the data. - - - -