| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alex Hunsaker <badalex(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add on_perl_init and proper destruction to plperl [PATCH] |
| Date: | 2010-01-27 21:53:07 |
| Message-ID: | 603c8f071001271353o1bcd9cc0ka227cd0ff95e435f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 27, 2010 at 4:51 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
>> Neither of those relate to the actions of perl source code.
>> To address that, instead of calling perl_destruct() to perform a
>> complete destruction I could just execute END blocks and object
>> destructors. That would avoid executing any system-level actions.
>
> Does perl_destruct() execute system-level actions, then? If so, then it seems prudent to either audit such actions or, as you say, call destructors directly.
What exactly do we mean by "system-level actions"? I mean, END blocks
can execute arbitrary code....
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-01-27 21:56:22 | Re: Add on_perl_init and proper destruction to plperl [PATCH] |
| Previous Message | David E. Wheeler | 2010-01-27 21:51:47 | Re: Add on_perl_init and proper destruction to plperl [PATCH] |