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

Re: determining a type oid from the name

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:32:43
Message-ID: 4F4550EB.2090106@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

On 02/22/2012 03:20 PM, Tom Lane wrote:
> 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?
>
> 			


Thanks, that might do the trick.

I fully agree it's not bulletproof, but I'm not sure what alternative 
there is.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2012-02-22 20:37:29
Subject: Re: pg_upgrade --logfile option documentation
Previous:From: Alvaro HerreraDate: 2012-02-22 20:32:09
Subject: Re: REASSIGN OWNED lacks support for FDWs

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