Re: plperl security

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

Tom Lane wrote:

>
>Recovering when you get an error is probably the trickiest part of this.
>
>

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?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Scott Marlowe 2004-07-07 15:26:07 Re: Nested Transactions, Abort All
Previous Message Zeugswetter Andreas SB SD 2004-07-07 13:17:31 Re: Point in Time Recovery