On Mon, Aug 26, 2019 at 8:12 AM Tom Lane wrote:
>
> Paul A Jungwirth writes:
> > Is it expected for flinfo to be null when using DirectFunctionCall*?
>
> Yes, per the comment on those functions:
>
> * These are for invocation of a specifically named function with a
> * directly-computed paramet
Paul A Jungwirth writes:
> On Mon, Aug 26, 2019 at 8:12 AM Tom Lane wrote:
>> Yes, per the comment on those functions:
>> * These are for invocation of a specifically named function with a
>> * directly-computed parameter list. Note that neither arguments nor result
>> * are allowed to be NULL.
Paul A Jungwirth writes:
> Is it expected for flinfo to be null when using DirectFunctionCall*?
Yes, per the comment on those functions:
* These are for invocation of a specifically named function with a
* directly-computed parameter list. Note that neither arguments nor result
* are allowed
Hello,
I'm writing a multirange_cmp function which calls range_cmp to compare
individual elements. It looks like this:
cmp = DatumGetInt32(DirectFunctionCall2(
range_cmp,
RangeTypePGetDatum(r1),
RangeTypePGetDatum(r2)));
But I get a segfault when range_cmp tries to reach
