Skip site navigation (1) Skip section navigation (2)

Re: BUG #5066: plperl issues with perl_destruct() and END blocks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5066: plperl issues with perl_destruct() and END blocks
Date: 2009-09-20 03:43:26
Message-ID: 16715.1253418206@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Sep 19, 2009 at 3:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> "Tim Bunce" <Tim(dot)Bunce(at)pobox(dot)com> writes:
>>> The plperl implementation doesn't call perl_destruct() during server
>>> shutdown.
>> 
>> Who cares? The process is going away anyway.

> END {} blocks can execute arbitrary code.  Perl users will expect them
> to be executed.

[ shrug... ]  As a database geek I find the lack of guarantees about
that to be entirely unsatisfying.  What exactly are you going to put
in that block?  If it's actually important, are you going to trust
a mechanism that doesn't have any crash safeness?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2009-09-20 07:08:39
Subject: Re: BUG #5068: LIKE
Previous:From: Robert HaasDate: 2009-09-20 03:26:16
Subject: Re: BUG #5066: plperl issues with perl_destruct() and END blocks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group