Re: [HACKERS] Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql

2009-04-13 Thread Kevin Grittner
Tom Lane t...@sss.pgh.pa.us wrote: Kevin Grittner kevin.gritt...@wicourts.gov writes: a change to CREATE FUNCTION such that there is an implied SET standard_compliant_strings FROM CURRENT Hopefully obvious, I meant standard_conforming_strings. it seems like a really bad idea. Then

Re: [HACKERS] Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql

2009-04-10 Thread Kevin Grittner
Andrew Gierth and...@tao11.riddles.org.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

Re: [HACKERS] Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql

2009-04-10 Thread Tom Lane
Kevin Grittner kevin.gritt...@wicourts.gov writes: 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