BUG #11761: range_in dosn't work via direct functional call - Mailing list pgsql-bugs

From olegjobs@mail.ru
Subject BUG #11761: range_in dosn't work via direct functional call
Date
Msg-id 20141022172703.2662.31056@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #11761: range_in dosn't work via direct functional call  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      11761
Logged by:          Oleg
Email address:      olegjobs@mail.ru
PostgreSQL version: 9.3.2
Operating system:   Ubuntu 64 14.04
Description:

This function test_ext_get_range(cstring) returns int4range:

Datum test_ext_get_range(PG_FUNCTION_ARGS)
{
   char *ts = PG_GETARG_CSTRING(0);

   return DirectFunctionCall3(range_in, CStringGetDatum(ts),
ObjectIdGetDatum(3904), Int32GetDatum(0);
}
In psql:
select test_ext_get_range('[1,1]');
error:
connection to the server was lost.

it seems to me that some memory problems because of "The range I/O functions
need a bit more cached info than other range
 * functions, so they store a RangeIOData struct in fn_extra, not just a
 * pointer to a type cache entry. "

pgsql-bugs by date:

Previous
From: olegjobs@mail.ru
Date:
Subject: BUG #11749: range_in, range_out dosn't work
Next
From: keyurgovande@gmail.com
Date:
Subject: BUG #11767: ODBC driver bug when fetching constant string columns