Skip site navigation (1) Skip section navigation (2)

Re: determining a type oid from the name

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Thom Brown <thom(at)linux(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: determining a type oid from the name
Date: 2012-02-22 20:20:35
Message-ID: 24151.1329942035@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Maybe I need to be more clear. The C code I'm writing will process 
> composites. I want to cache the Oids of certain non-builtin types in the 
> function info's fn_extra, and then be able to test whether or not the 
> fields in the composites are of those types.

What's your basis for identifying those types in the first place?
Name?  Doesn't seem terribly robust if the other extension can be
installed in some random schema.  But anyway, something in
parser/parse_type.c ought to help you with that --- maybe
parseTypeString?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-02-22 20:22:29
Subject: Re: pg_upgrade --logfile option documentation
Previous:From: Bruce MomjianDate: 2012-02-22 20:01:10
Subject: Re: pg_upgrade --logfile option documentation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group