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

Commitdad0e20

Browse files
committed
Mention "PostgreSQL"'s hashes as slower/similar to btree.
1 parent1415a83 commitdad0e20

File tree

3 files changed

+23
-19
lines changed

3 files changed

+23
-19
lines changed

‎doc/src/sgml/diskusage.sgml‎

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/diskusage.sgml,v 1.1 2002/06/13 05:15:22 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/diskusage.sgml,v 1.2 2002/06/21 19:06:44 momjian Exp $
33
-->
44

55
<chapter id="diskusage">
@@ -22,10 +22,12 @@ $Header: /cvsroot/pgsql/doc/src/sgml/diskusage.sgml,v 1.1 2002/06/13 05:15:22 mo
2222
</para>
2323

2424
<para>
25-
You can monitor disk space from two places; from inside
26-
<application>psql</> and from the command line using
27-
<application>contrib/oid2name</>. Using <application>psql</> you can
28-
issue queries to see the disk usage for any table:
25+
You can monitor disk space from three places: from
26+
<application>psql</> using <command>VACUUM</> information, from
27+
<application>psql</> using <application>contrib/dbsize</>, and from
28+
the command line using <application>contrib/oid2name</>. Using
29+
<application>psql</> on a recently vacuumed (or analyzed) database,
30+
you can issue queries to see the disk usage of any table:
2931
<programlisting>
3032
play=# SELECT relfilenode, relpages
3133
play-# FROM pg_class
@@ -38,10 +40,10 @@ play-# WHERE relname = 'customer';
3840
</para>
3941

4042
<para>
41-
Each page is typically 8 kilobytes. <literal>relpages</> is only
42-
updated by <command>VACUUM</> and <command>ANALYZE</>. To show the
43-
space used by <acronym>TOAST</> tables, use a query based on the heap
44-
relfilenode:
43+
Each page is typically 8 kilobytes.(Remember,<literal>relpages</>
44+
is onlyupdated by <command>VACUUM</> and <command>ANALYZE</>.) To
45+
show thespace used by <acronym>TOAST</> tables, use a query based on
46+
the heaprelfilenode shown above:
4547
<programlisting>
4648
play=# SELECT relname, relpages
4749
play-# FROM pg_class

‎doc/src/sgml/indices.sgml‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/indices.sgml,v 1.33 2002/06/2116:52:00 momjian Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/indices.sgml,v 1.34 2002/06/2119:06:44 momjian Exp $ -->
22

33
<chapter id="indexes">
44
<title id="indexes-title">Indexes</title>
@@ -181,10 +181,11 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
181181
</synopsis>
182182
<note>
183183
<para>
184-
Testing has shown hash indexes to be similar or slower than btree
185-
indexes, and the index size and build time for hash indexes is much
186-
worse. Hash indexes also suffer poor performance under high
187-
concurrency. For these reasons, hash index use is discouraged.
184+
Testing has shown PostgreSQL's hash indexes to be similar or slower
185+
than btree indexes, and the index size and build time for hash
186+
indexes is much worse. Hash indexes also suffer poor performance
187+
under high concurrency. For these reasons, hash index use is
188+
discouraged.
188189
</para>
189190
</note>
190191
</para>

‎doc/src/sgml/ref/create_index.sgml‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.33 2002/06/2116:52:00 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.34 2002/06/2119:06:44 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -330,10 +330,11 @@ ERROR: Cannot create index: 'index_name' already exists.
330330
the <literal>=</literal> operator.
331331
</para>
332332
<para>
333-
Testing has shown hash indexes to be similar or slower than btree
334-
indexes, and the index size and build time for hash indexes is much
335-
worse. Hash indexes also suffer poor performance under high
336-
concurrency. For these reasons, hash index use is discouraged.
333+
Testing has shown PostgreSQL's hash indexes to be similar or slower
334+
than btree indexes, and the index size and build time for hash
335+
indexes is much worse. Hash indexes also suffer poor performance
336+
under high concurrency. For these reasons, hash index use is
337+
discouraged.
337338
</para>
338339

339340
<para>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp