-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Reuse connections in postgresql metricsets #12603
Conversation
8e1b3e1
to
801f9ad
Compare
801f9ad
to
e68e916
Compare
|
||
results, err := postgresql.QueryStats(db, "SELECT * FROM pg_stat_statements") | ||
ctx := context.Background() | ||
results, err := m.QueryStats(ctx, "SELECT * FROM pg_stat_statements") |
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.
I'm guessing metricset Close
won't cancel these requests, I guess it would be unexpected for them to leak, but it could be worth it to handle ctx cancellation?
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.
Right, Close
doesn't cancel running queries, they will be executed till they finish. I wouldn't expect leaks because of that.
Not sure if it would worth to hande cancelation here, we'd need to keep a thread safe list of cancelation functions available on close. Once we have #11981 or similar we will be able to cancel the parent context when calling the closers.
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.
++ I thought about that PR too. That said, you don't really need to keep a list, isn't it? When creating the metricset you can create a Background context, use it in all fetch operations and cancel it on close.
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.
Having that that PR is moving (:crossed_fingers:) I'm ok with leaving this for update after it's merged
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.
That said, you don't really need to keep a list, isn't it? When creating the metricset you can create a Background context, use it in all fetch operations and cancel it on close.
Yes, this would be another option, but I think this is what should be done in a general what by #11981. Doing it this way here has some disadvantages, we'd be hiding the context inside the metricset and it would be a different one to the one received by Fetch
if #11981 is implemented.
Having that that PR is moving (crossed_fingers) I'm ok with leaving this for update after it's merged
Yeah, let me move this forward 🙂
Reuse connections in PostgreSQL metricsets instead of opening and
closing one on each fetch.
Fixes #12504