Re: BUG #5066: plperl issues with perl_destruct() and END blocks
От | David Fetter |
---|---|
Тема | Re: BUG #5066: plperl issues with perl_destruct() and END blocks |
Дата | |
Msg-id | 20090921165327.GJ31599@fetter.org обсуждение исходный текст |
Ответ на | Re: BUG #5066: plperl issues with perl_destruct() and END blocks (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: BUG #5066: plperl issues with perl_destruct() and END
blocks
Re: BUG #5066: plperl issues with perl_destruct() and END blocks |
Список | pgsql-bugs |
On Mon, Sep 21, 2009 at 12:06:30PM -0400, Alvaro Herrera wrote: > David Fetter escribió: > > > Taken literally, that would mean, "the last action before the > > backend exits," but at least to me, that sounds troubling for the > > same reasons that "end of transaction" triggers do. What happens > > when there are two different END blocks in a session? > > The manual is clear that both are executed. So it is, but does order matter, and if so, how would PostgreSQL know? > > With connection poolers, backends can last quite awhile. Is it OK > > for the END block to run hours after the rest of the code? > > This is an interesting point -- should END blocks be called on > DISCARD ALL? ENOCLUE Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
В списке pgsql-bugs по дате отправления: