On Jan 12, 2011, at 11:22 AM, Alex Hunsaker wrote: > Personally, I think the point of a compatibility GUC is that at some > point in the distant future we can get rid of it. If we default to > the old behavior thats going to be harder to do. +1 for defaulting to > the new behavior.
+1 > [ 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) ] Yeah, but the removal of Safe.pm actually *improved* compatibility. This patch, without the GUC, would break it. Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
