Re: standard_conforming_strings

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, Alex Hunsaker <badalex(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: standard_conforming_strings
Date: 2010-07-18 16:42:59
Message-ID: 9AF6416B-42C2-47AB-8338-DFBD08035638@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2010-07-18 16:51:28 Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock
Previous Message Bruce Momjian 2010-07-18 16:05:44 Re: crash-recovery replay of CREATE TABLESPACE is broken in HEAD