postgrespro.git / summary / log / commit / refs

commit    1c2ff3ef07d25ca4d291d35f8a31fe513fde58ab
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Fri May 22 00:28:38 2020 +0000

    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


 doc/src/sgml/config.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 9f2a4a2470..a2694e548a 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4925,7 +4925,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>


[parent: c20fd088f1c5]