|
1 | 1 | <!-- |
2 | 2 | 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 $ |
4 | 4 | --> |
5 | 5 |
|
6 | 6 | <chapter id="catalogs"> |
|
289 | 289 | </indexterm> |
290 | 290 |
|
291 | 291 | <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">. |
295 | 296 | </para> |
296 | 297 |
|
297 | 298 | <table> |
|
453 | 454 | </tgroup> |
454 | 455 | </table> |
455 | 456 |
|
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 | | - |
470 | 457 | </sect1> |
471 | 458 |
|
472 | 459 |
|
|