Replies: 2 comments 2 replies
-
Sequel is never going to preemptively raise an error instead of waiting for locks to be released. If you want to avoid waiting indefinitely, then you might want to look into https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-STATEMENT-TIMEOUT |
Beta Was this translation helpful? Give feedback.
0 replies
-
Got it! Can the statement timeout be set via Sequel natively when creating the connection? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Complete description of the issue
When having a sharded connection pool with a
read_only
option, once a transaction is opened if a statement that locks the table is executed and on a subsequent query a select operation on the locked table is done then Sequel will hang due to the select query waiting for the locked table to be released.Simplest Possible Self-Contained Example Showing the Issue
SQL Log (if any)
Expected Behavior
An error be raised instead of getting stuck waiting indefinitely for the lock to be released.
Ruby Version
3.2.0
Sequel Version
5.74.0
Beta Was this translation helpful? Give feedback.
All reactions