Re: Controlling changes in plpgsql variable resolution

On Oct 19, 2009, at 12:05 PM, Tom Lane wrote:

>> What about adopting the modifier syntax you're adding to COPY?
>
> Where exactly would you put the modifier, and why is that better than
> the existing #option convention?

CREATE OR REPLACE FUNCTION foo()
RETURNS BOOLEAN
LANGUAGE plpgsql WITH opt1, opt2
AS $$...$$;

That is, the specification of options is made outside of the language  
in question. It might only effect a particular language (plpgsql in  
this case) and be ignored otherwise (or trigger an exception), but  
it's clean and very much like what you have elsewhere.

Best,

David