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-06-23 19:50:16 |
Message-ID: | 200806231950.m5NJoGp19077@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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? :-)
I would like to add a TODO item for this, but I am concerned that people
running functions with different standard_conforming_strings values
would have function syntax errors on mismatch. Is that acceptable?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-06-23 21:11:35 | Re: BUG #4053: libpq documentation should express clearly, that integers are passed in network octet order |
Previous Message | Tom Lane | 2008-06-23 18:05:34 | Re: Abnormal termination of PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-06-23 19:52:36 | Dept of ugly hacks: eliminating padding space in system indexes |
Previous Message | Simon Riggs | 2008-06-23 13:16:56 | Re: pg_stat_statements |