constants for return value from PQftype?

I'm trying to build the PoPy PostgreSQL/Python interface so that
I can use PostgreSQL with Zope, and I'm having some problems:

First, I had to modify PoPy.h so that it would not include
<postgres.h> and <catalog/pg_type.h>, which don't seem to be
moved into the normal include path by the install. I think
that they've been obsoleted and postgres.h has been essentially
replaced with <libpq-fe.h>. In any case, it seems that I got
to this point:

gcc -fPIC -Wstrict-prototypes -Wall -O6 -fomit-frame-pointer -I/usr/local/include/python2.2 -I/usr/local/lib/python2.2/config -DHAVE_CONFIG_H=1 -I/usr/local/pgsql/include -Wall -DVERSION=\"3.0-beta1\" -c ././PoPy.c -o ./PoPy.o
././PoPy.c: In function `PoPy_converter':
././PoPy.c:77: `BOOLOID' undeclared (first use in this function)
././PoPy.c:77: (Each undeclared identifier is reported only once
././PoPy.c:77: for each function it appears in.)
././PoPy.c:83: `INT2OID' undeclared (first use in this function)
././PoPy.c:84: `INT4OID' undeclared (first use in this function)
././PoPy.c:89: `DATEOID' undeclared (first use in this function)
././PoPy.c:90: `TIMEOID' undeclared (first use in this function)
././PoPy.c:91: `TIMESTAMPOID' undeclared (first use in this function)
././PoPy.c:95: `PG_BINARY' undeclared (first use in this function)
././PoPy.c:110: `FLOAT4OID' undeclared (first use in this function)
././PoPy.c:111: `FLOAT8OID' undeclared (first use in this function)
././PoPy.c: At top level:

/***

Here's the code:

***/

ftype = PQftype(result, field);

if(PQgetisnull(result, tuple, field)) {
Py_INCREF(Py_None);
return Py_None;
}

ftype = (ftype>1000 && ftype < 1028?PG_ARRAY:ftype);
switch(ftype) {
case PG_ARRAY_BOOL:
res = PoPy_array_handler(PQgetvalue(result,tuple,field),0);
break;
case PG_ARRAY:

/*****/

I looked through the headers and the documentation. the PG_xxx constants
don't seem to be in the the user include files. I can't seem to find PQftype in
the documentation, or any hint as to what it should be returning. Shouldn't
these constants, or something like them be somewhere in the include files?

--
Adam Haberlach | Who buys an eight-processor machine and then
adam(at)newsnipple(dot)com | watches 30 movies on it all at the same time?
http://newsnipple.com | Beats me. They told us they could sell it, so
| we made it. -- George Hoffman, Be Engineer