On 01/29/2010 09:01 PM, Tom Lane wrote:
Maybe. We concluded in the April 2009 thread that
standard_conforming_strings = ON had gotten little or no field testing,
and I don't see any strong reason to hope that it's gotten much more
since then. It would be rather surprising if there *aren't* any lurking
bugs in one piece or another of client-side code. And I don't think
that we should be so myopic as to consider that problems in drivers and
so forth are not of concern.
Not to contradict any justifiable investigation, but just as a data point:
All of my installations use:
backslash_quote = off # on, off, or safe_encoding
escape_string_warning = off
standard_conforming_strings = on
I have not encountered any problems so far. I use PostgreSQL in about 10
production applications (too tired to count them out :-) ), from psql to
PHP to Perl to Java. I had also assumed this feature was tested and
supported when I enabled it, as it seemed to me to be the only sensible
implementation, and it was consistent with my interpretation of SQL. I
had done some testing before enabling it the first time and was
satisfied with the results.
I would be all for making this change in an orderly fashion pursuant to
some agreed-on plan. But cramming it in at the last minute because of
an essentially marketing-driven change of version name isn't good
project management, and I'm seriously afraid that doing so would bite
us in the rear.
An actual plan here might look like "let's flip it before 9.1alpha1
so we can get some alpha testing cycles on it" ...
Yep.
Cheers,
mark
--
Mark Mielke<m...@mielke.cc>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
