From: | Alexey Klyukin <alexk(at)commandprompt(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Alex Hunsaker <badalex(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David E(dot) Wheeler <david(at)kineticode(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: arrays as pl/perl input arguments [PATCH] |
Date: | 2011-01-12 20:13:25 |
Message-ID: | 16D4421A-2E7A-4D10-94A0-75C623F092CE@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan 12, 2011, at 9:36 PM, Alvaro Herrera wrote:
> Excerpts from Alex Hunsaker's message of mié ene 12 16:22:55 -0300 2011:
>
>> [ Id actually vote for _not_ having a compatibility option at all, we
>> change more major things than this IMHO every major release. (And even
>> then some major things in minor releases, for example the removal of
>> Safe.pm) ]
>
> I think the main question here is: how loudly is existing code going to
> break? If the breakage is silent, it's going to be very problematic.
> If functions fail to run at all, then we can live without the
> compatibility option.
Not really loud. Perl won't even complain when you try to interpret a
reference as a string.
Since almost everyone votes for making the new behavior a default option I'm
inclined to do that change, although I'm against throwing out the
compatibility option. There are many other reasons except for PL/Perl for
people to upgrade to 9.1, let's not force them to rewrite their Perl code
if they were not planning to do that.
/A
--
Alexey Klyukin
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-01-12 20:17:08 | Re: arrays as pl/perl input arguments [PATCH] |
Previous Message | Joel Jacobson | 2011-01-12 20:09:31 | Re: pg_depend explained |