aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2002-08-05 02:30:50 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2002-08-05 02:30:50 +0000
commit07f9682de43ce53fcd6d86744f610cacfabc60bb (patch)
tree2415db60be54912154c9c8f8834fb94f33fa5bca /doc/src
parentac1a3dcf24e182a1cc9a136246b7f18a8a64bbd5 (diff)
downloadpostgresql-07f9682de43ce53fcd6d86744f610cacfabc60bb.tar.gz
postgresql-07f9682de43ce53fcd6d86744f610cacfabc60bb.zip
Preliminary code review for anonymous-composite-types patch: fix breakage
of functions returning domain types, update documentation for typtype, move get_typtype to lsyscache.c (actually, resurrect the old version), add defense against creating pseudo-typed table columns, fix some bogus list-parsing in grammar. Issues remain with respect to alias handling and type checking; Joe is on those.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/catalogs.sgml9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 573815388fe..38dbe32aad7 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1,6 +1,6 @@
<!--
Documentation of the system catalogs, directed toward PostgreSQL developers
- $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.51 2002/08/02 18:15:04 tgl Exp $
+ $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.52 2002/08/05 02:30:46 tgl Exp $
-->
<chapter id="catalogs">
@@ -3201,8 +3201,9 @@
<entry>
<structfield>typtype</structfield> is <literal>b</literal> for
a base type, <literal>c</literal> for a complex type (i.e.,
- a table's row type), or <literal>d</literal> for a derived type (i.e.,
- a domain). See also <structfield>typrelid</structfield>
+ a table's row type), <literal>d</literal> for a derived type (i.e.,
+ a domain), or <literal>p</literal> for a pseudo-type. See also
+ <structfield>typrelid</structfield>
and <structfield>typbasetype</structfield>.
</entry>
</row>
@@ -3235,7 +3236,7 @@
<structfield>typtype</structfield>), then this field points to
the <structfield>pg_class</structfield> entry that defines the
corresponding table. A table could theoretically be used as a
- composite data type, but this is not fully functional.
+ composite data type, but this is only partly functional.
Zero for non-complex types.
</entry>
</row>