| From: | alex(at)pilosoft(dot)com |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Michael Fuhr <mike(at)fuhr(dot)org>, Mike Rylander <mrylander(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DBD::PgSPI 0.02 |
| Date: | 2004-12-06 19:34:33 |
| Message-ID: | Pine.LNX.4.44.0412061430530.10941-100000@bawx.pilosoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, 6 Dec 2004, Tom Lane wrote:
> alex(at)pilosoft(dot)com writes:
> > On Mon, 6 Dec 2004, Andrew Dunstan wrote:
> >> . how to turn it on for trusted plperl
>
> > Eh, you don't turn it on. You install the package and it works ;)
>
> Really? If the plperl Safe opmask allows that, we've got some problems.
Errr my bad. I keep confusing trusted/untrusted. It does not allow it, nor
should it.
The purpose of PgSPI is to write 'middleware' solutions in perl - the idea
is that you can take a piece of existing client-side code and make a
server-side stored procedure out of it in a minute without any changes to
the code.
For quick access from trusted code, spi_exec should just do fine.
-alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-06 19:36:00 | Re: DBD::PgSPI 0.02 |
| Previous Message | Andrew M | 2004-12-06 19:33:59 | Re: SSL confirmation - (could not accept SSL connection: sslv3 alert certificate unknown ) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-06 19:36:00 | Re: DBD::PgSPI 0.02 |
| Previous Message | Michael Fuhr | 2004-12-06 19:28:53 | Re: DBD::PgSPI 0.02 |