Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql
Date
Msg-id 878wm8gs70.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabled inplpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
Tom> Back to the point at hand: do we want to look at making plpgsqlTom> 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)

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql
Next
From: "Kevin Grittner"
Date:
Subject: Re: Re: [BUGS] BUG #4027: backslash escapingnotdisabledinplpgsql