From: | Michael Blakeley <mike(at)blakeley(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: plperl crashing backend |
Date: | 2000-09-04 00:22:32 |
Message-ID: | p05001107b5d89b7a7e17@blakeley.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 8:07 PM -0400 9/3/2000, Tom Lane wrote:
>Michael Blakeley <mike(at)blakeley(dot)com> writes:
>> I'm running postgresql 7.0.1 on Solaris 2.6, with the latest patch
>> cluster. I've compiled pg and Perl 5.6.0 with gcc 2.9.5-2.
>
>Hmm. Your trace shows
>
>> open("/usr/local/pgsql/lib/plperl.so", O_RDONLY) = 40
>>
>>open("/usr/local/lib/perl5/5.6.0/sun4-solaris/auto/Opcode/Opcode.so",
>>O_RDONLY) = 40
>> open("/usr/lib/libperl.so", O_RDONLY) = 40
>
>I'd have expected libperl to be opened from somewhere in the same
>general area as the Opcode module, say
>/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE/libperl.so
>if the shape of the Perl install tree hasn't changed recently.
>Perhaps you are pulling in some older, incompatible release of Perl
>that came with your OS?
No, the postgres backend was trying to load libperl.so from /usr/lib,
so I put a symbolic link there. It's all 5.6.0.
-- Mike
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-09-04 00:37:23 | Viability of VARLENA_FIXED_SIZE() |
Previous Message | Jason J. Czerak | 2000-09-04 00:20:42 | Is it me or... |