Re: Add on_perl_init and proper destruction to plperl [PATCH] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date
Msg-id 16547.1264635199@sss.pgh.pa.us
Whole thread Raw
In response to Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
Responses Re: Add on_perl_init and proper destruction to plperl [PATCH]  ("David E. Wheeler" <david@kineticode.com>)
Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
List pgsql-hackers
Tim Bunce <Tim.Bunce@pobox.com> writes:
> On Wed, Jan 27, 2010 at 11:28:02AM -0500, Tom Lane wrote:
>> Really?  We've found that gprof, for instance, doesn't exactly have
>> "zero interaction with the rest of the backend" --- there's actually
>> a couple of different bits in there to help it along, including a
>> behavioral change during shutdown.  I rather doubt that Perl profilers
>> would turn out much different.

> Devel::NYTProf (http://blog.timbunce.org/tag/nytprof/) has zero
> interaction with the rest of the backend.

I don't have to read any further than the place where it says "doesn't
work if you call both plperl and plperlu" to realize that that's quite
false.  Maybe we have different definitions of what a software
interaction is...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]
Next
From: "David E. Wheeler"
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]