Re: standard_conforming_strings

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: pgsql-hackers@postgresql.org, Michael Meskes <meskes@postgresql.org>
Date: 2010-07-20T02:00:40Z
Lists: pgsql-hackers
On Mon, Jul 19, 2010 at 8:32 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Mon, Jul 19, 2010 at 5:04 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> On sön, 2010-07-18 at 09:42 -0700, David E. Wheeler wrote:
>>> On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote:
>>>
>>> > I think there are two ways we can do this, seeing that most appear to be
>>> > in favor of doing it in the first place:  Either we just flip the
>>> > default, make a note in the release notes, and see what happens.  Or we
>>> > spend some time now and make, say, a list of driver versions and
>>> > application versions that work with standard_conforming_strings = on,
>>> > and then decide based on that, and also make that list a public resource
>>> > for packagers etc.
>>>
>>> Do both. Turn them on, then make a list and inform driver maintainers who need to update. They've got a year, after all.
>>
>> Here we go then:
>> http://wiki.postgresql.org/wiki/Standard_conforming_strings
>
> Looks like a good start.  We might want to make an "open items for
> 9.1" page and, as a first such open item, add a link to this page.
>
> Since it seems we have consensus, I will commit the patch.

So it turns out that (at least) the hstore and ECPG regression tests
depend on the default setting of standard_conforming_strings.  I have
taken a crack at fixing this...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company