From: | Bborie Park <bkpark(at)ucdavis(dot)edu> |
---|---|
To: | |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Passing NULL to a function called with OidFunctionCall3 |
Date: | 2011-11-11 00:47:21 |
Message-ID: | 4EBC7099.3000203@ucdavis.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/10/2011 04:43 PM, Tom Lane wrote:
> Bborie Park<bkpark(at)ucdavis(dot)edu> writes:
>> I'm trying to make use of OidFunctionCall3 and am wondering how to
>> resolve an issue. I need to be able to pass to the function called with
>> OidFunctionCall3 a NULL and am having difficulty figuring out how.
>
> You can't. Those convenience functions are not designed to support null
> arguments (nor null results, for that matter). If they did, they'd be
> so much more complicated to use as to not be worth the bother.
>
> You'll need to write out something comparable to what OidFunctionCall3
> does internally; look into fmgr.c. It would behoove you also to make
> sure that the function is not strict before you call it with a null,
> because a function that is strict is entirely entitled to dump core
> on you if you do that.
>
> regards, tom lane
>
Thanks Tom!
--
Bborie Park
Programmer
Center for Vectorborne Diseases
UC Davis
530-752-8380
bkpark(at)ucdavis(dot)edu
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-11-11 00:55:34 | Re: VACUUM touching file but not updating relation |
Previous Message | Tom Lane | 2011-11-11 00:43:02 | Re: Passing NULL to a function called with OidFunctionCall3 |