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. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
