Thread: standard_conforming_strings 'on' for 8.3?

Are we going to turn on standard_conforming_strings for 8.3?  We
discussed the idea when we added it in 8.1, and enabled the backslash
warning in 8.2.  We have gotten almost no pushback on the warning, so it
seems enabling it might be good.  Right now, for default
postgresql.conf, users are getting warnings for backslashes in non-E''
strings, so once we set standard_conforming_strings to 'on', we would
turn off the warning.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +

Bruce Momjian <bruce@momjian.us> writes:
> Are we going to turn on standard_conforming_strings for 8.3?

I'd be inclined to wait a bit longer, i.e., 8.4, seeing that this is
intended to be a short release cycle.  8.2 has not been out long enough
to draw any meaningful conclusions about whether we have gotten "almost
no pushback" --- for instance it's probably not shipped in any major
Linux distros yet.
        regards, tom lane

Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Are we going to turn on standard_conforming_strings for 8.3?
> 
> I'd be inclined to wait a bit longer, i.e., 8.4, seeing that this is
> intended to be a short release cycle.  8.2 has not been out long enough
> to draw any meaningful conclusions about whether we have gotten "almost
> no pushback" --- for instance it's probably not shipped in any major
> Linux distros yet.

OK, makes sense. I am just noticing some of the documentation isn't
clear on mentioning standard_conforming_strings in all places, so I will
update that.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +