I didn't see it documented anywhere that a 0 in attypid of pg_attribute,
and given the note on the need to match pg_type lest failure seems to
warrant the mention.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: src/include/catalog/pg_attribute.h
===================================================================
RCS file: /projects/cvsroot/pgsql-server/src/include/catalog/pg_attribute.h,v
retrieving revision 1.104
diff -c -r1.104 pg_attribute.h
*** src/include/catalog/pg_attribute.h 4 Aug 2003 02:40:11 -0000 1.104
--- src/include/catalog/pg_attribute.h 4 Sep 2003 22:30:44 -0000
***************
*** 50,56 ****
* defines the data type of this attribute (e.g. int4). Information
* in that instance is redundant with the attlen, attbyval, and
* attalign attributes of this instance, so they had better match or
! * Postgres will fail.
*/
Oid atttypid;
--- 50,57 ----
* defines the data type of this attribute (e.g. int4). Information
* in that instance is redundant with the attlen, attbyval, and
* attalign attributes of this instance, so they had better match or
! * Postgres will fail. An entry of 0 signifies a dropped column and
! * will have no match.
*/
Oid atttypid;
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
