From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
---|---|
To: | bricklen <bricklen(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: plperlu function caused a segmentation fault |
Date: | 2011-08-24 19:11:11 |
Message-ID: | CAFaPBrS1vOKf4gD7ty2BmbAc08kPQAQ89uoxqX6gaqeUKC2bEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Aug 24, 2011 at 12:32, bricklen <bricklen(at)gmail(dot)com> wrote:
> On Wed, Aug 24, 2011 at 11:28 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I wonder if there is something wonky about your Perl installation.
>
> I tested originally on two other 9.0.4 databases and there were no
> issues at all. I'll have to assume that you are correct about the Perl
> setup on that server -- I'm quite leery of doing anything else with
> that server as it is a production db.
Hrm, do simple plperlu functions break it? I can't tell from your
report if plperlu seems completely broken or if something in your
quoted function seems to be the culprit.
If
CREATE OR REPLACE FUNCTION plperlu_noop() returns void as $$ $$
language plperlu;
select plperlu_noop();
works fine, I would wager someone upgraded perl and forgot to
recompile (or upgrade?) postgres along with it. That or you have more
than one perl installed and its somehow picking the wrong libperl...
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2011-08-24 19:13:41 | Re: What is postgresql status? |
Previous Message | Raymond O'Donnell | 2011-08-24 19:08:05 | Re: What is postgresql status? |