Sven Willenberger <sven@dmv.com> writes:
> Yes, on these systems, perl was build with -Dusemymalloc (and
> concurrently -Ui_malloc) so there could very well be an issue with
> malloc pools going awry. Doing a quick dig reveals that Linux tends to
> build perl (by default) with the system malloc which may explain why
> your script did not display this same behavior.
I can confirm that my copy is not using mymalloc:
$ perl -V | grep -i alloc
usemymalloc=n, bincompat5005=undef
$
regards, tom lane
