From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 22 May 2020 00:28:38 +0000 (-0400)
Subject: doc:  suggest 1.1 as a random_page_cost value for SSDs
X-Git-Tag: REL_11_9~102
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b75f73dc0cf792171cacdc536327807dbd496205;p=thirdparty%2Fpostgresql.git

doc:  suggest 1.1 as a random_page_cost value for SSDs

Reported-by: yigong hu

Discussion: https://postgr.es/m/CAOxFffcourucFqSk+tZA13ErS3XRYkDy6EeaPff4AvHGiEEuug@mail.gmail.com

Backpatch-through: 9.5
---

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 37d044be981..73bc969bace 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4012,7 +4012,8 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
         the database is smaller than the total server memory, decreasing
         random_page_cost can be appropriate.  Storage that has a low random
         read cost relative to sequential, e.g. solid-state drives, might
-        also be better modeled with a lower value for random_page_cost.
+        also be better modeled with a lower value for random_page_cost,
+        e.g., <literal>1.1</literal>.
        </para>
 
        <tip>