Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane), pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql
Date: 2009-04-10 20:38:27
Message-ID: 878wm8gs70.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

Tom> Back to the point at hand: do we want to look at making plpgsql
Tom> respect the GUC?

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?

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2009-04-10 20:46:09 Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql
Previous Message Josh Berkus 2009-04-10 20:35:06 Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-04-10 20:46:09 Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql
Previous Message l0rins 2009-04-10 20:37:22 Re: unable to install tsearch2 on PostgreSQL 8.3.7 successfully