From: Fujii Masao <fujii@postgresql.org>
Date: Fri, 16 Dec 2016 16:25:29 +0000 (+0900)
Subject: Add missing documentation for effective_io_concurrency tablespace option.
X-Git-Tag: REL_10_BETA1~1246
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=4e344c2cf4ff00ca38ea0035bc137dab95fdd0c0;p=postgresql.git

Add missing documentation for effective_io_concurrency tablespace option.

The description of effective_io_concurrency option was missing in ALTER
TABLESPACE docs though it's included in CREATE TABLESPACE one.

Back-patch to 9.6 where effective_io_concurrency tablespace option was added.

Michael Paquier, reported by Marc-Olaf Jaschke
---

diff --git a/doc/src/sgml/ref/alter_tablespace.sgml b/doc/src/sgml/ref/alter_tablespace.sgml
index d9b2a133b10..2f411050012 100644
--- a/doc/src/sgml/ref/alter_tablespace.sgml
+++ b/doc/src/sgml/ref/alter_tablespace.sgml
@@ -83,14 +83,15 @@ ALTER TABLESPACE <replaceable>name</replaceable> RESET ( <replaceable class="PAR
     <listitem>
      <para>
       A tablespace parameter to be set or reset.  Currently, the only
-      available parameters are <varname>seq_page_cost</> and
-      <varname>random_page_cost</>.  Setting either value for a particular
-      tablespace will override the planner's usual estimate of the cost of
-      reading pages from tables in that tablespace, as established by
-      the configuration parameters of the same name (see
-      <xref linkend="guc-seq-page-cost">,
-      <xref linkend="guc-random-page-cost">).  This may be useful if one
-      tablespace is located on a disk which is faster or slower than the
+      available parameters are <varname>seq_page_cost</>,
+      <varname>random_page_cost</> and <varname>effective_io_concurrency</>.
+      Setting either value for a particular tablespace will override the
+      planner's usual estimate of the cost of reading pages from tables in
+      that tablespace, as established by the configuration parameters of the
+      same name (see <xref linkend="guc-seq-page-cost">,
+      <xref linkend="guc-random-page-cost">,
+      <xref linkend="guc-effective-io-concurrency">).  This may be useful if
+      one tablespace is located on a disk which is faster or slower than the
       remainder of the I/O subsystem.
      </para>
     </listitem>