From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, Alex <alex(at)meerkatsoft(dot)com>, Lada 'Ray' Lostak <ray(at)unreal64(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: SELECT Question |
Date: | 2003-11-20 17:56:00 |
Message-ID: | 3FBD0030.6020108@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>>CREATE OR REPLACE FUNCTION test(int,int) RETURNS SETOF int AS '
>>BEGIN
>> FOR i IN $1..$2 LOOP
>> RETURN NEXT i;
>> END LOOP;
>> RETURN;
>>END;
>>' LANGUAGE 'plpgsql' STRICT IMMUTABLE;
>
> I was thinking of proposing that we provide something just about like
> that as a standard function (written in C, not in plpgsql, so that it
> would be available whether or not you'd installed plpgsql). There are
> some places in the information_schema that desperately need it ---
> right now, the value of FUNC_MAX_ARGS is effectively hard-wired into
> some of the information_schema views, which means they are broken if
> one changes that #define. We could fix this if we had a function like
> the above and exported FUNC_MAX_ARGS as a read-only GUC variable.
I've been really busy on other-than-postgres stuff lately, but I'm
planning to carve out time next week to start doing some 7.5
development. I'll take this one if you want.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-11-20 18:22:04 | Re: tsearch2 installation |
Previous Message | Tom Lane | 2003-11-20 17:45:51 | Re: SELECT Question |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2003-11-20 18:24:31 | fix compile warning |
Previous Message | Tom Lane | 2003-11-20 17:45:51 | Re: SELECT Question |