From: | olegjobs(at)mail(dot)ru |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #11761: range_in dosn't work via direct functional call |
Date: | 2014-10-22 17:27:03 |
Message-ID: | 20141022172703.2662.31056@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 11761
Logged by: Oleg
Email address: olegjobs(at)mail(dot)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. "
From | Date | Subject | |
---|---|---|---|
Next Message | keyurgovande | 2014-10-22 21:22:10 | BUG #11767: ODBC driver bug when fetching constant string columns |
Previous Message | Tom Lane | 2014-10-22 14:35:24 | Re: BUG #11638: Transaction safety fails when constraints are dropped and analyze is done |