summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2020-05-21 20:28:38 -0400
committerBruce Momjian <bruce@momjian.us>2020-05-21 20:28:38 -0400
commit7bf6b3e0075538598a1fb02a11f3080678814ed5 (patch)
treef80bf66ffe46662379689eddbf065d610992c22f
parentd594e4cd73ea30fd64af0a9d438a8ad498dd50e7 (diff)
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
-rw-r--r--doc/src/sgml/config.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 92681cf4530..d56f4274070 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3650,7 +3650,8 @@ include_dir 'conf.d'
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>