Re: BUG #5066: plperl issues with perl_destruct() and END blocks
От | Alvaro Herrera |
---|---|
Тема | Re: BUG #5066: plperl issues with perl_destruct() and END blocks |
Дата | |
Msg-id | 20090921160630.GF29793@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: BUG #5066: plperl issues with perl_destruct() and END blocks (David Fetter <david@fetter.org>) |
Ответы |
Re: BUG #5066: plperl issues with perl_destruct() and END
blocks
Re: BUG #5066: plperl issues with perl_destruct() and END blocks |
Список | pgsql-bugs |
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. > 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? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-bugs по дате отправления: