Re: Controlling changes in plpgsql variable resolution

"David E. Wheeler" <david@kineticode.com> writes:
> On Oct 19, 2009, at 11:47 AM, Tom Lane wrote:
>> 2. Also invent a #option syntax that allows the GUC to be overridden
>> per-function.  (Since the main GUC is SUSET, we can't just use a
>> per-function SET to override it.  There are other ways we could do  
>> this but none seem less ugly than #option...)

> 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?
        regards, tom lane