Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit c6521b1

Browse files
committed
Write some real documentation about the index access method API.
1 parent 67ff800 commit c6521b1

File tree

6 files changed

+852
-315
lines changed

6 files changed

+852
-315
lines changed

doc/src/sgml/catalogs.sgml

Lines changed: 5 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!--
22
Documentation of the system catalogs, directed toward PostgreSQL developers
3-
$PostgreSQL: pgsql/doc/src/sgml/catalogs.sgml,v 2.95 2005/01/05 23:42:03 tgl Exp $
3+
$PostgreSQL: pgsql/doc/src/sgml/catalogs.sgml,v 2.96 2005/02/13 03:04:15 tgl Exp $
44
-->
55

66
<chapter id="catalogs">
@@ -289,9 +289,10 @@
289289
</indexterm>
290290

291291
<para>
292-
The catalog <structname>pg_am</structname> stores information about index access
293-
methods. There is one row for each index access method supported by
294-
the system.
292+
The catalog <structname>pg_am</structname> stores information about index
293+
access methods. There is one row for each index access method supported by
294+
the system. The contents of this catalog are discussed in detail in
295+
<xref linkend="indexam">.
295296
</para>
296297

297298
<table>
@@ -453,20 +454,6 @@
453454
</tgroup>
454455
</table>
455456

456-
<para>
457-
An index access method that supports multiple columns (has
458-
<structfield>amcanmulticol</structfield> true) <emphasis>must</>
459-
support indexing null values in columns after the first, because the planner
460-
will assume the index can be used for queries on just the first
461-
column(s). For example, consider an index on (a,b) and a query with
462-
<literal>WHERE a = 4</literal>. The system will assume the index can be used to scan for
463-
rows with <literal>a = 4</literal>, which is wrong if the index omits rows where <literal>b</> is null.
464-
It is, however, OK to omit rows where the first indexed column is null.
465-
(GiST currently does so.)
466-
<structfield>amindexnulls</structfield> should be set true only if the
467-
index access method indexes all rows, including arbitrary combinations of null values.
468-
</para>
469-
470457
</sect1>
471458

472459

doc/src/sgml/filelist.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/filelist.sgml,v 1.41 2005/01/10 00:04:38 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/filelist.sgml,v 1.42 2005/02/13 03:04:15 tgl Exp $ -->
22

33
<!entity history SYSTEM "history.sgml">
44
<!entity info SYSTEM "info.sgml">
@@ -77,7 +77,7 @@
7777
<!entity catalogs SYSTEM "catalogs.sgml">
7878
<!entity geqo SYSTEM "geqo.sgml">
7979
<!entity gist SYSTEM "gist.sgml">
80-
<!entity indexcost SYSTEM "indexcost.sgml">
80+
<!entity indexam SYSTEM "indexam.sgml">
8181
<!entity nls SYSTEM "nls.sgml">
8282
<!entity plhandler SYSTEM "plhandler.sgml">
8383
<!entity protocol SYSTEM "protocol.sgml">

0 commit comments

Comments
 (0)