From: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Daniel(dot)Hutchison(at)rokaconsulting(dot)com, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: PLPerl not installed correctly? |
Date: | 2010-04-23 10:31:12 |
Message-ID: | 20100423103112.GL78694@timac.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Tue, Apr 20, 2010 at 11:21:55AM -0400, Tom Lane wrote:
> "Daniel Hutchison" <Daniel(dot)Hutchison(at)rokaconsulting(dot)com> writes:
> > I've been experiencing problems getting any plperl function working, and I
> > believe the problem lies in the actual plperl installation not due to my
> > rusty perl memories. For example, the very simple plperl example in the
> > comprehensive documentation (at
> > http://www.postgresql.org/docs/8.4/interactive/plperl-funcs.html)
> > Returns something odd (at least to me, also with little postgresql
> > experience):
> > prod1=> select perl_max(1,2);
> > ERROR: invalid input syntax for integer: "CODE(0x1f6d13c)"
>
> I'm going to guess that your perl installation doesn't match the version
> of perl your postgresql installation was built against.
Or perhaps it's picking up the wrong version of the plperl shared lib.
This should work for finding the perl (not plperl) version:
create function perl_ver() RETURNS void AS $$ warn $] $$ language plperl;
select perl_ver();
NOTICE: 5.008008 at line 1.
Tim.
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Linkous | 2010-04-23 15:05:28 | install both i386 and x86_64 libs |
Previous Message | Tom Lane | 2010-04-22 22:16:55 | Re: set default: question |