Input Function (domain_in) Call

From: Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Input Function (domain_in) Call
Date: 2006-08-19 06:15:59
Message-ID: 20060819061559.GA1404@alamut
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I was using OidInputFunctionCall() to cast a basic type into a domain
type. But when I saw

/*
* As above, for I/O functions identified by OID. These are only to be
* used in seldom-executed code paths. They are not only slow but leak
* memory.
*/
Datum
OidInputFunctionCall(Oid functionId, char *str,
Oid typioparam, int32 typmod)

comment in backend/utils/fmgr/fmgr.c, I started to consider my decision.
Is this the right way to use domain_in() function? Which way would you
suggest? Or is there a totally different way to accomplish basic type to
domain transition?

Regards.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Naz Gassiep 2006-08-19 07:44:46 Re: pg_dump schema breakup
Previous Message Bruce Momjian 2006-08-19 04:55:25 Re: Windows 2000 Support