>
> 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/
