-
-
Notifications
You must be signed in to change notification settings - Fork 233
select from mon$statements lockup [CORE1561] #1980
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
Comments
Commented by: @hvlad I can't reproduce it - select * from mon$statements worked fine (results shown immediately) and i have ability to kill long running statemetnt |
Commented by: Saulius Vabalas (svabalas) Did You try it on 2.1 Beta 2 or on upcoming RC1? It could be related to CORE1562 Dmitry fixed. |
Commented by: @hvlad I tried it with current HEAD i.e. after beta 2 |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 RC1 [ 10201 ] assignee: Dmitry Yemanov [ dimitr ] |
Modified by: @pcisarWorkflow: jira [ 13374 ] => Firebird [ 14028 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Saulius Vabalas (svabalas)
select from mon$statements is not responding when other connection is running high load query:
- Start two ISQL instances and connect to same DB
- on #1 connection execute statement:
select count(*) from rdb$triggers,rdb$triggers,rdb$triggers,rdb$triggers,rdb$triggers;
- on #2 connection execute statement: select * from mon$statements;
#2 SQL will not return any results until #1 is running. This makes impossible to identify high load running queries nor any other queries when at least one of HL queries is running.
Commits: 1f1a8c8
The text was updated successfully, but these errors were encountered: