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
Query timeout on the server [CORE658] #1024
Comments
Modified by: @pcisarassignee: Dmitry Yemanov [ dimitr ] => |
Modified by: @dyemanovFix Version: 3.0 [ 10048 ] assignee: Dmitry Yemanov [ dimitr ] SF_ID: 807910 => |
Modified by: @dyemanovTarget: 2.5.0 [ 10221 ] Fix Version: 2.5 Alpha 1 [ 10224 ] Fix Version: 3.0.0 [ 10048 ] => |
Modified by: @pcisarWorkflow: jira [ 10682 ] => Firebird [ 15056 ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Open [ 1 ] Fix Version: 2.5 Beta 1 [ 10251 ] Fix Version: 2.5 Alpha 1 [ 10224 ] => |
Commented by: Pabloj (pabloj_sourceforge) It would also be nice to have per user "quotas" in resources or max allowed query cost |
Commented by: pabloj (pabloj) I see this is planned for 3.0 Alpha , could you give details on what will be implemented? |
Commented by: @dyemanov I was thinking about the following timeout values: - database-level (specified in firebird.conf) As for quotas, they belong to a much wider topic (including also CPU load, memory and disk space usage, etc) and thus require more thinking. They, if considered, should go into a separate ticket, IMO. |
Commented by: @mrotteveel In for example JDBC the query timeout is a property of the statement handle, and similar in http://ADO.net and ODBC. This also feels like a more natural place than database- or transaction level. |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] => Vlad Khorsun [ hvlad ] Fix Version: 3.0 Beta 1 [ 10332 ] => |
Modified by: @dyemanovFix Version: 4.0 Alpha 1 [ 10731 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @pcisar
Relate to CORE985
Is replaced by CORE5488
Votes: 13
SFID: 807910#
Submitted By: pcisar
The server should have built-in support to ensure that
a query cannot run 'away'. A parameter in the server
config file should establish the maximum query
execution time.
The text was updated successfully, but these errors were encountered: