Movatterモバイル変換


[0]ホーム

URL:


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

Sign up
Appearance settings

Commit0221bc9

Browse files
committed
Mention increasing sort_mem during a restore.
1 parent7d06fc0 commit0221bc9

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

‎doc/src/sgml/runtime.sgml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.194 2003/07/22 20:29:13 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.195 2003/07/23 20:30:35 momjian Exp $
33
-->
44

55
<Chapter Id="runtime">
@@ -887,7 +887,9 @@ SET ENABLE_SEQSCAN TO OFF;
887887
times the value of <varname>SORT_MEM</varname>. Sort operations are used
888888
by <literal>ORDER BY</>, merge joins, and <command>CREATE INDEX</>.
889889
Hash tables are used in hash joins, hash-based aggregation, and
890-
hash-based processing of <literal>IN</> subqueries.
890+
hash-based processing of <literal>IN</> subqueries. Because
891+
<command>CREATE INDEX</> is used when restoring a database, it might
892+
be good to temporary increase this value during a restore.
891893
</para>
892894
</listitem>
893895
</varlistentry>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp