Re: plperl vs. bytea - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plperl vs. bytea
Date
Msg-id 549.1178416797@sss.pgh.pa.us
Whole thread Raw
In response to plperl vs. bytea  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: plperl vs. bytea
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> After discussing some possibilities, we decided that maybe 
> the best approach would be to allow a custom GUC variable that would 
> specify a list of types to be passed in binary form with no conversion, e.g.

>   plperl.pass_as_binary = 'bytea, other-type'

At minimum this GUC would have to be superuser-only, and even then the
security risks seem a bit high.  But the real problem with this thinking
is the same one I already pointed out to Theo: why do you think this
issue is plperl-specific?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Integer datetimes
Next
From: Andrew Dunstan
Date:
Subject: Re: plperl vs. bytea