function attributes - Mailing list pgsql-hackers

From Andrew Dunstan
Subject function attributes
Date
Msg-id 4D03FADF.4000205@pgexperts.com
Whole thread Raw
Responses Re: function attributes  ("David E. Wheeler" <david@kineticode.com>)
Re: function attributes  (Robert Haas <robertmhaas@gmail.com>)
Re: function attributes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Yesterday I did a bit of work on allowing bytea values to be passed into 
and out of plperl in binary format, effectively removing the need to 
escape and de-escape them. (The work can be seen on he plperlargs branch 
of my development repo at 
<https://github.com/adunstan/postgresql-dev/commits/plperlargs/>).

At the moment the behaviour is triggered by a custom setting 
(plperl.pass_binary_bytea), but this isn't really satisfactory. We could 
turn it on  permanently, but that would break a lot of legacy code. What 
we really need is a way of marking a function with some attributes. Of 
course, we could put it in the program text like plpgsql's 
#variable_conflict, but that's really rather ugly. The grammar already 
has an attribute mechanism for functions, and ISTM we just need to 
extend that a bit to allow setting of function attributes reasonably 
flexibly, much as we can now specify format options on EXPLAIN or we'll 
soon be able to specify options for foreign tables.

Thoughts?

cheers

andrew


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: auxiliary functions for record type
Next
From: "David E. Wheeler"
Date:
Subject: Re: function attributes