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

From Andrew Dunstan
Subject Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date
Msg-id 4B606876.3050508@dunslane.net
Whole thread Raw
In response to Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:
> Indeed, AFAICS the major *point* of these additions is to allow people
> to insert unknown other functionality that is likely to interact
> with the rest of the backend; a prospect that doesn't make me feel
> better about it.
>
>   

No. The major use case we've seen for END blocks is to allow a profiler 
to write its data out. That should have zero interaction with the rest 
of the backend.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]
Next
From: Tom Lane
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]