Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 1c2ff3e

Browse filesBrowse files
bmomjianbmomjian
committed
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
1 parent c20fd08 commit 1c2ff3e
Copy full SHA for 1c2ff3e

File tree

Expand file treeCollapse file tree

1 file changed

+2
-1
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-1
lines changed

‎doc/src/sgml/config.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/config.sgml
+2-1Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4925,7 +4925,8 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
49254925
the database is smaller than the total server memory, decreasing
49264926
random_page_cost can be appropriate. Storage that has a low random
49274927
read cost relative to sequential, e.g. solid-state drives, might
4928-
also be better modeled with a lower value for random_page_cost.
4928+
also be better modeled with a lower value for random_page_cost,
4929+
e.g., <literal>1.1</literal>.
49294930
</para>
49304931

49314932
<tip>

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.