-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for connection closed listeners #525
Conversation
Look at |
Please clarify.
|
I am un-drafting this PR because I don't know how to write proper tests for this code. Maintainers are free to commit to my PR, and if anyone else wants to pick up the PR, feel free to make a new one based on mine. |
Can any maintainer please take a look at this and try to write up some test cases? |
it's a very important feature, can somebody check it? |
Termination listener reads better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you elaborate on the name "termination listener"? How does "close listener" read worse?
In the phrase "close listener" the word "close" reads like a distance adjective, i.e. "a near listener". "Termination listener" is simply better English. |
Thank you so much! |
#421 (comment)
Other than that, how does this look? The following code demonstrates the functionality. It prints True after a postgres server restart, then exits: