aboutsummaryrefslogtreecommitdiff
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
commita87209ce7e1270b3a48e107c981a7035196d662b (patch)
tree5570a5887c4032b638f6180a715981e6b18c23e6
parent388d7f8c62b407005f56b6262a678d9fb96ea18c (diff)
downloadpostgresql-a87209ce7e1270b3a48e107c981a7035196d662b.tar.gz
postgresql-a87209ce7e1270b3a48e107c981a7035196d662b.zip
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 e5041aca7c6..f279fe5cada 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4761,7 +4761,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>