On Jan 12, 2011, at 8:52 PM, David E. Wheeler wrote:

> 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.

Well, neither me (I haven't used much of the guts api there).

> 
>> 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. If there is a strong dislike of the proposed 'compatibility' GUC option - I think I can change the existing patch to incorporate array string representation into the reference-holding SV quite easily.
> 
> Andrew's objections have merit. So perhaps just add this patch to the commit fest as is?

Already done :)

/A


--
Alexey Klyukin
The PostgreSQL Company - Command Prompt, Inc.

In response to

• Re: arrays as pl/perl input arguments [PATCH] at 2011-01-12 18:52:42 from David E. Wheeler

Responses

• Re: arrays as pl/perl input arguments [PATCH] at 2011-01-15 22:48:28 from Alex Hunsaker

pgsql-hackers by date

Next:	From: Joel Jacobson	Date: 2011-01-12 20:09:31
	Subject: Re: pg_depend explained
Previous:	From: Robert Haas	Date: 2011-01-12 19:59:20
	Subject: Re: WIP: Range Types