Re: plperl security - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plperl security
Date
Msg-id 1904.1089426993@sss.pgh.pa.us
Whole thread Raw
In response to Re: plperl security  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [Plperlng-devel] Re: plperl security  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> OK, I have a setup that instead of refusing to load trusted functions if 
> the Safe version is not up to date, forces them to error out by calling 
> elog(ERROR...), thus:

> andrew=# select tval();
> ERROR:  trusted perl functions disabled - please upgrade perl Safe 
> module to at least 2.09

> This seems like perfectly reasonable recovery to me. Thoughts?

Works for me --- and it doesn't leak memory across repeated failures,
right?

Patch please?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: bug in DROP TABLESPACE
Next
From: Philip Warner
Date:
Subject: Re: [PATCHES] Fixes for pg_dump and ownership/acl problems