Re: BUG #4027: backslash escaping not disabled in plpgsql - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #4027: backslash escaping not disabled in plpgsql
Date
Msg-id 200812160334.mBG3YfK13570@momjian.us
Whole thread Raw
In response to Re: BUG #4027: backslash escaping not disabled in plpgsql  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-bugs
Peter Eisentraut wrote:
> Tom Lane wrote:
> > plpgsql does not consider standard_conforming_strings --- it still uses
> > backslash escaping in its function bodies regardless.  Since the
> > language itself is not standardized, I see no particular reason that
> > standard_conforming_strings should govern it.
>
> I think plpgsql should behave either consistently with the rest of PostgreSQL
> or with Oracle, which it is copied from.
>
> > I believe the reason for
> > not changing it was that it seemed too likely to break existing
> > functions, with potentially nasty consequences if they chanced to be
> > security definers.
>
> Is this actually true or did we just forget it? :-)

Did we ever address this?

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4582: Renaming sequences and default value
Next
From: Jan-Peter Seifert
Date:
Subject: Re: BUG #4582: Renaming sequences and default value