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 perhaps a note in the PL/pgSQL docs about the importance of specifying that clause if the function contains any character string literals which include a backslash? Such a note should probably point out that without this clause, the runtime value of any such literal will be dependent on the value of standard_conforming_strings when the plan is generated. I think that many will find that behavior surprising; so if it's not feasible to change it, we should at least document it. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
