Re: Dynamic binding in plpgsql function

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pierre Racine <Pierre(dot)Racine(at)sbf(dot)ulaval(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dynamic binding in plpgsql function
Date: 2011-03-02 15:05:23
Message-ID: AANLkTi=iTDQyeUijCqrkquFjq7VMnVPbuF3PAsu91_3a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Mar 2, 2011 at 8:54 AM, Dmitriy Igrishin <dmitigr(at)gmail(dot)com> wrote:
> 2011/3/2 Merlin Moncure <mmoncure(at)gmail(dot)com>
>> Lane...http://postgresql.1045698.n5.nabble.com/improvise-callbacks-in-plpgsql-td2052928.html
>> (for whom nary a day goes by that I am not thankful for his tireless
>> efforts).
>
> Ahh, thanks to Tom Lane then !
> And thank you for the link of interesting topic from past :-)

yes...in the old days there was a lot more reason to do this because
there was no 'using' for execute and it was a lot more difficult to
coerce record types, arrays, etc into text format for passing. today,
I would probably use execute unless I already had C library in the
backend and was *really* concerned about speed.

merlin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pierre Racine 2011-03-02 15:06:53 Re: Dynamic binding in plpgsql function
Previous Message Dmitriy Igrishin 2011-03-02 14:54:14 Re: Dynamic binding in plpgsql function