Re: plperl security

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, plperlng-devel(at)pgfoundry(dot)org
Subject: Re: plperl security
Date: 2004-07-10 02:36:33
Message-ID: 1904.1089426993@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2004-07-10 02:47:09 Re: [PATCHES] Fixes for pg_dump and ownership/acl problems
Previous Message Bruce Momjian 2004-07-10 02:07:07 Re: bug in DROP TABLESPACE