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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
