| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | KeithW(at)narrowpathinc(dot)com |
| Cc: | PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: plperl user function |
| Date: | 2005-04-21 20:38:01 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
>
> Another question: Is there an issue with using the untrusted perl language?
IIRC you have to be a postgresql superuser (postgres) to execute an
untrusted language function.
> If the code is tested and working is there any real reason to continue to have
> "use strict;" and "use warnings;" in the function?
Only for manageability in the future.
Sincerely,
Joshua D. Drake
>
> Kind Regards,
> Keith
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedication Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-04-21 20:42:50 | Re: plperl user function |
| Previous Message | Joshua D. Drake | 2005-04-21 20:36:58 | Re: plperl user function |