-
-
Notifications
You must be signed in to change notification settings - Fork 82
Crash when using 'SET statement_timeout=x' #347
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
Labels
bug
Something isn't working
Comments
Thanks for the issue. Do you want to try to tackle this problem? |
A stepped through the stack and had a 🤯moment. So I think that someone with more knowledge of the library would be faster. |
gwynne
added a commit
that referenced
this issue
Apr 27, 2023
fabianfett
added a commit
to fabianfett/postgres-nio
that referenced
this issue
Apr 27, 2023
Merged
fabianfett
added a commit
to fabianfett/postgres-nio
that referenced
this issue
Apr 27, 2023
fabianfett
added a commit
to fabianfett/postgres-nio
that referenced
this issue
Apr 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I want to prevent rogue queries from hogging up my database connections and therefore use
SET statement_timeout=10000;
to let the server kill long running queries.
This leads to a crash in
ConnectionStateMachine.swift#845
with the messageTried to cancel stream without active query
whenever PostgreSQL kills a query.This is the stacktrace:
and the state machine object:
The text was updated successfully, but these errors were encountered: