-
Notifications
You must be signed in to change notification settings - Fork 1k
processlist: Prevent crash due to SQLITE_TOOBIG #5165
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
Conversation
Summary of ChangesHello @wazir-ahmed, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a critical stability issue where excessively long queries could lead to Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request introduces a mechanism to prevent crashes from SQLITE_TOOBIG
errors by truncating long queries in the processlist. It adds a new configuration variable, processlist_max_query_length
, for both MySQL and PostgreSQL to control the maximum length of queries stored. Additionally, it refactors the processlist configuration handling by grouping related variables into a struct and passing it as an argument, which improves code clarity and maintainability by removing the reliance on thread-local variables. The changes are well-structured and address the core issue effectively. I've added a few suggestions for improving robustness and code style.
- Add new mysql/pgsql variable `processlist_max_query_length`. - Min: 1K - Max: 32M - Default: 2M - Truncate current query based on the configuration before inserting into `stats_*_processlist` tables. - Refactor/fix code related to other processlist configurations. 1. `session_idle_show_processlist` value was not updated in `ProxySQL_Admin.variables`. 2. Pass processlist config as an argument to `MySQL_Threads_Handler::SQL3_Processlist` instead of using thread-local variables. Signed-off-by: Wazir Ahmed <[email protected]>
4a1f09a
to
5219d4b
Compare
|
processlist_max_query_length
.stats_*_processlist
tables.session_idle_show_processlist
value was not updated inProxySQL_Admin.variables
.MySQL_Threads_Handler::SQL3_Processlist
instead of using thread-local variables.