-
Notifications
You must be signed in to change notification settings - Fork 73
remove finalizer and use LazyCleaner implementation from pgjdbc #1625
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
base: main
Are you sure you want to change the base?
Conversation
| } | ||
|
|
||
| private boolean startThread() { | ||
| Thread thread = threadFactory.newThread(new Runnable() { |
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.
Should the thread be a daemon thread?
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.
Actually we do not use a daemon thread in pgjdbc
|
|
||
| public void releaseResources() { | ||
| this.pluginManager.releaseResources(); | ||
| if (this.pluginService instanceof CanReleaseResources) { |
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.
Should we clean up pluginManager similar way?
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.
we would have to pass pluginManager into LazyCleaner, but sure
|
Hold off on doing anything with this. Upstream we are looking at creating a multi-version jar with java 11 and using the built-in cleaner and some modifications to this implementation |
Summary
see $subject
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.