Re: BUG #4027: backslash escaping not disabled in plpgsql

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jonathan Guthrie <jguthrie(at)brokersys(dot)com>
Subject: Re: BUG #4027: backslash escaping not disabled in plpgsql
Date: 2008-03-12 19:37:00
Message-ID: 200803121937.m2CJb0w05212@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Agreed. standard_conforming_strings should affect _all_ strings.
>
> We might need another transition period over a few releases with a
> separate "plpgsql_standard_conforming_strings" parameter. Just changing it
> immediately is perhaps a bit risky.

We haven't even enabled standard_conforming_strings by default yet. It
was added as changeable in 8.2. Is this never going to be enabled by
default?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-03-12 19:37:59 Re: 8.3.0 backend segfaults
Previous Message Peter Eisentraut 2008-03-12 19:28:59 Re: BUG #4027: backslash escaping not disabled in plpgsql

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-12 19:41:31 Re: Why is there a tsquery data type?
Previous Message Peter Eisentraut 2008-03-12 19:28:59 Re: BUG #4027: backslash escaping not disabled in plpgsql