|
1 | 1 | <!--
|
2 | 2 | Documentation of the system catalogs, directed toward PostgreSQL developers
|
3 |
| - $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.54 2002/08/24 15:00:45 tgl Exp $ |
| 3 | + $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.55 2002/08/28 15:02:55 tgl Exp $ |
4 | 4 | -->
|
5 | 5 |
|
6 | 6 | <chapter id="catalogs">
|
|
890 | 890 | <title>pg_class</title>
|
891 | 891 |
|
892 | 892 | <para>
|
893 |
| - <structname>pg_class</structname> catalogs tables and mostly |
| 893 | + <structname>pg_class</structname> catalogs tables and most |
894 | 894 | everything else that has columns or is otherwise similar to a
|
895 | 895 | table. This includes indexes (but see also
|
896 | 896 | <structname>pg_index</structname>), sequences, views, and some
|
897 |
| - kinds of special relation. Below, when we mean all of these |
| 897 | + kinds of special relation; see <structfield>relkind</>. |
| 898 | +. Below, when we mean all of these |
898 | 899 | kinds of objects we speak of <quote>relations</quote>. Not all
|
899 | 900 | fields are meaningful for all relation types.
|
900 | 901 | </para>
|
|
957 | 958 | <entry>relfilenode</entry>
|
958 | 959 | <entry><type>oid</type></entry>
|
959 | 960 | <entry></entry>
|
960 |
| - <entry>Name of the on-disk file of this relation</entry> |
| 961 | + <entry>Name of the on-disk file of this relation; 0 if none</entry> |
961 | 962 | </row>
|
962 | 963 |
|
963 | 964 | <row>
|
|
1030 | 1031 | <entry></entry>
|
1031 | 1032 | <entry>
|
1032 | 1033 | 'r' = ordinary table, 'i' = index, 'S' = sequence, 'v' = view,
|
1033 |
| - 's' = special, 't' = secondary TOAST table |
| 1034 | + 'c' = composite type, 's' = special, 't' = TOAST table |
1034 | 1035 | </entry>
|
1035 | 1036 | </row>
|
1036 | 1037 |
|
|
3127 | 3128 | <para>
|
3128 | 3129 | This catalog stores information about data types. Scalar types
|
3129 | 3130 | (<quote>base types</>) are created with <command>CREATE TYPE</command>.
|
3130 |
| - A complex type is also created for each table in the database, to |
| 3131 | + A complex type is automatically created for each table in the database, to |
3131 | 3132 | represent the row structure of the table. It is also possible to create
|
| 3133 | + complex types with <command>CREATE TYPE AS</command>, and |
3132 | 3134 | derived types with <command>CREATE DOMAIN</command>.
|
3133 | 3135 | </para>
|
3134 | 3136 |
|
|
3242 | 3244 | <entry>
|
3243 | 3245 | If this is a complex type (see
|
3244 | 3246 | <structfield>typtype</structfield>), then this field points to
|
3245 |
| - the <structfield>pg_class</structfield> entry that defines the |
3246 |
| - corresponding table. A table could theoretically be used as a |
3247 |
| - composite data type, but this is only partly functional. |
| 3247 | + the <structname>pg_class</structname> entry that defines the |
| 3248 | + corresponding table. (For a free-standing composite type, the |
| 3249 | + <structname>pg_class</structname> entry doesn't really represent |
| 3250 | + a table, but it is needed anyway for the type's |
| 3251 | + <structname>pg_attribute</structname> entries to link to.) |
3248 | 3252 | Zero for non-complex types.
|
3249 | 3253 | </entry>
|
3250 | 3254 | </row>
|
|
0 commit comments