From: | oberpwd(at)anubis(dot)network(dot)com (Wade D(dot) Oberpriller) |
---|---|
To: | peter_e(at)gmx(dot)net (Peter Eisentraut) |
Cc: | oberpwd(at)anubis(dot)network(dot)com (Wade D(dot) Oberpriller), pgsql-general(at)postgresql(dot)org (general-help postgresql) |
Subject: | Re: PL/Perl on Solaris |
Date: | 2000-11-27 15:27:34 |
Message-ID: | 200011271527.JAA27908@truck.network.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)network(dot)com
>
> 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(at)gmx(dot)net http://yi.org/peter-e/
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Wade D. Oberpriller | 2000-11-27 15:30:57 | Re: |
Previous Message | Peeter Smitt | 2000-11-27 14:25:31 | nested table |