PL/Perl on Solaris

Wade D. Oberpriller writes:

Is anyone using the PL/Perl language in PostgreSQL on a Solaris machine?
If so, how did you get it to work? I am having difficulty getting it to run,
I believe I am having problems with the dynamically linked shared libraries.

OS version, compiler version, linker version, PostgreSQL version, example
input, error messages. Details, man! ;-)

--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/

Wade D. Oberpriller writes:

Is anyone using the PL/Perl language in PostgreSQL on a Solaris machine?
If so, how did you get it to work? I am having difficulty getting it to run,
I believe I am having problems with the dynamically linked shared libraries.

OS version, compiler version, linker version, PostgreSQL version, example
input, error messages. Details, man! ;-)

Solaris 2.5.1
gcc 2.7.2.2
linker: ld: Software Generation Utilities (SGU)
SunOS/ELF (LK-2.0 (S/I) - versioning)
PostgreSQL 7.0.2

I am able to compile PL/Perl okay. I can do a createlang for PL/Perl and add
it to my database. I can create functions with LANGUAGE set to 'plperl'. Once
I attempt to execute the function, the postgres server dies with status 11.

--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/

Wade Oberpriller

Hello,

I've found the cause of all my troubles with PLPerl. When building Perl
5.005_03, there is an option to use the Perly version of malloc. I, of course,
used the default (which is yes). All is well in the Perl world, however when
PLPerl attempts to use this alternative memory allocation scheme it doesn't
play well with PostgreSQL.

So the moral of the story is answer NO to using the Perl malloc if you intend
to use PLPerl (at least on a 2.5.1 Solaris machine running Perl 5.005_03).

Wade Oberpriller
StorageTek
oberpwd@network.com

oberpwd@anubis.network.com (Wade D. Oberpriller) writes:

I've found the cause of all my troubles with PLPerl. When building
Perl 5.005_03, there is an option to use the Perly version of
malloc. I, of course, used the default (which is yes). All is well in
the Perl world, however when PLPerl attempts to use this alternative
memory allocation scheme it doesn't play well with PostgreSQL.

Is there a way to fix that, or at least detect that libperl has been
configured that way?

I thought we had this dependency documented somewhere, but evidently
it's not very clearly stated ...

regards, tom lane