From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: function attributes |
Date: | 2010-12-12 02:45:28 |
Message-ID: | AANLkTikUejTiL38oC7_e2zWV8g-G_wEZ9QfRABFCySCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Dec 11, 2010 at 9:28 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> On 12/11/2010 09:16 PM, Robert Haas wrote:
>>
>> Well, you could set that GUC (plperl.pass_binary_bytea) on a function
>> without changing any syntax on at all.
>>
>> CREATE FUNCTION name (args) ... SET plperl.pass_binary_bytea = true;
>
> Oh, good point. I'd forgotten about that. I'll experiment and see if I can
> break it :-)
I guess one problem with that approach is that the scoping of the
parameter change will be dynamic rather than lexical.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-12-12 02:47:49 | Re: keeping a timestamp of the last stats reset (for a db, table and function) |
Previous Message | Robert Haas | 2010-12-12 02:32:01 | Re: unlogged tables |