Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> (Come to think of it, doesn't Perl normally use its very own private malloc?
> Maybe there's an issue right there ...)
Perl can be built either way. It should work to have two different malloc's
running side by side as long as the correct free() is always called. Ie, as
long as perl doesn't hand any data structures to postgres expecting postgres
to free it or vice versa.
--
greg