Alex Hunsaker <bada...@gmail.com> writes:
> On Fri, Jan 29, 2010 at 13:42, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> [ still bearing scars from the 8.3 implicit-cast business, which we
>> didn't think would generate nearly the backlash it did... ]
> Yeah that was my first reaction. But then again we also have a guc
> they can change back.
"There's a GUC for it" is NOT a helpful answer; if there's one thing
that we've learned the hard way over the past years, it's that GUCs
don't solve compatibility problems. Applications don't know to set
them, and having the wrong setting can easily become a security hole
(particularly for this one).
I stand by the position that it's way too late in the cycle for
insufficiently-thought-out proposals for major behavioral changes.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
