| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <pgsql-hackers(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Gierth" <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Subject: | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql |
| Date: | 2009-04-10 20:46:09 |
| Message-ID: | 49DF69C1.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
> Surely what matters is the value of the GUC at the time that you did
> the CREATE FUNCTION, not the value at the time you happen to be
> calling it?
Well, that's a change I'm arguing for. That would require both the
plpgsql parser change Tom is talking about, and a change to CREATE
FUNCTION such that there is an implied SET standard_compliant_strings
FROM CURRENT -- which is something I've suggested a couple times;
there's been no explicit response to that.
See back here in the thread for some behavior which surprised me:
http://archives.postgresql.org/pgsql-hackers/2009-04/msg00519.php
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-04-10 21:16:14 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |
| Previous Message | Andrew Gierth | 2009-04-10 20:38:27 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-04-10 20:57:26 | Re: pg_restore dependencies |
| Previous Message | Andrew Gierth | 2009-04-10 20:38:27 | Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql |