From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Alexey Klyukin <alexk(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: arrays as pl/perl input arguments [PATCH] |
Date: | 2011-01-13 07:06:33 |
Message-ID: | AANLkTi=b9VBXGv2wnB64zD67Gh+Yn2MU9t=_NmQGc+Kx@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 12, 2011 at 22:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David E. Wheeler" <david(at)kineticode(dot)com> writes:
>> On Jan 12, 2011, at 5:14 AM, Alexey Klyukin wrote:
>>> You mean packing both a string representation and a reference to a single SV * value?
>
>> Dunno, I'm not a guts guy.
>
>> I haven't considered that (lack of extensive perlgus-foo) although I
>> think that's an interesting idea. One drawback would be that it would
>> require both conversion to a string format and to a perl reference,
>> performing unnecessary actions during every time arrays are passed to a
>> pl/perl function.
>
> I had supposed that it would be possible to do the string conversion
> lazily, ie, only if the string value was actually demanded.
Yep, In-fact if we wanted we could even die (or throw an exception in
other language speak :) ) when the string value is demanded.
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2011-01-13 07:13:09 | Re: Error code for "terminating connection due to conflict with recovery" |
Previous Message | KaiGai Kohei | 2011-01-13 06:10:45 | Re: sepgsql contrib module |