Skip site navigation (1) Skip section navigation (2)

Re: plperl user function

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: (view raw or whole 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.


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 -

In response to


pgsql-interfaces by date

Next:From: Michael FuhrDate: 2005-04-21 20:42:50
Subject: Re: plperl user function
Previous:From: Joshua D. DrakeDate: 2005-04-21 20:36:58
Subject: Re: plperl user function

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group