Message 82266 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	jwp
Recipients	jwp, jwpye, mutkuk, vstinner
Date	2009年02月16日.19:54:33
SpamBayes Score	0.0024065406
Marked as misclassified	No
Message-id	<1234814120.95.0.356060520737.issue1195571@psf.upfronthosting.co.za>

Content
I had actually forgotten that this was still open. Anything I can do to help speed this along? In case nobody remembers, the purpose of this was to provide a facility to embedded applications that allows for a more graceful shutdown in fatal error situations. My original use-case was for a PostgreSQL PL extension where an abort() is quite undesirable as it would take down the entire cluster(yeah, all the postmaster processes). IIRC, the only thoughts "against" it were rather for trying to remove FatalErrors entirely. hepl?

Content

I had actually forgotten that this was still open. Anything I can do to
help speed this along?
In case nobody remembers, the purpose of this was to provide a facility
to embedded applications that allows for a more graceful shutdown in
fatal error situations. My original use-case was for a PostgreSQL PL
extension where an abort() is quite undesirable as it would take down
the entire cluster(yeah, all the postmaster processes).
IIRC, the only thoughts "against" it were rather for trying to remove
FatalErrors entirely.
hepl?

History
Date	User	Action	Args
2009年02月16日 19:55:21	jwp	set	recipients: + jwp, vstinner, jwpye, mutkuk
2009年02月16日 19:55:20	jwp	set	messageid: <1234814120.95.0.356060520737.issue1195571@psf.upfronthosting.co.za>
2009年02月16日 19:54:34	jwp	link	issue1195571 messages
2009年02月16日 19:54:33	jwp	create

homepage