Re: Planning error in dynamic string creation in plpgsql

That is not an option either. This is for a publicly released extension and
I'm really not going to go requiring another scripting language be
installed, especially an untrusted one.

--
Keith Fiske
Database Administrator
OmniTI Computer Consulting, Inc.
http://www.keithf4.com

On Sun, Jan 5, 2014 at 11:44 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>wrote:

> On 01/05/2014 08:34 PM, Keith Fiske wrote:
>
>> Actually, that doesn't work right. Gives weird results when the column
>> is an integer
>>
>> Example:
>>
>> keith=# select min(col1), max(col1) from
>> partman_test.time_static_table_p2014_01_01;
>> min | max
>> -----+-----
>> 86 | 100
>> (1 row)
>>
>> keith=# select min(col1::text), max(col1::text) from
>> partman_test.time_static_table_p2014_01_01;
>> min | max
>> -----+-----
>> 100 | 99
>> (1 row)
>>
>
>
> Should have added to my previous post, that when I want to deal with truly
> dynamic values I use plpythonu. plpgsql is very useful but it does not like
> types changing under it. plpythonu deals with that better.
>
>
>
>>
>>
>> --
>> Keith Fiske
>> Database Administrator
>> OmniTI Computer Consulting, Inc.
>> http://www.keithf4.com
>>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
>