Skip to content
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

option: mysql show processlist instead of show full processlist #231

Open
mikegriffin opened this issue Jul 13, 2020 · 1 comment
Open
Assignees

Comments

@mikegriffin
Copy link

mikegriffin commented Jul 13, 2020

It would be nice to have a non-FULL processlist configuration that continues to default to full processlist (call a new print_mysql_full_procs):

USEMYSQLFULLPROCESSLIST=yes

print_mysql_procs()
..

mysqladmin processlist

print_mysql_full_procs()
mysqladmin -v processlist

Whether the above is implemented or not, it would be good to correct existing logging which incorrectly claims that "show processlist" was issued.

This feature request is to avoid having to suppress all error messages going to email from cron, when you regularly hit an error around max_allowed_packet, as might happen if you are often doing a large INSERT for bulk loading (eg you do not want to change the defaults for all local clients)

@tonyskapunk
Copy link
Contributor

Hi @mikegriffin thanks for opening this request.

I see the concern, currently the USEMYSQLPROCESSLIST is using -v in the process list command in a couple of places:

-v processlist \

-v processlist \

I think is easy to create a new function to distinguish between PROCESSLIST and FULL PROCESSLIST.

USEMYSQL is not enabled by default nor USEMYSQLPROCESSLIST

recap/src/recap

Lines 95 to 99 in b4d296a

declare -r default_USEMYSQLPROCESSLIST="no"
DOTMYDOTCNF="${default_DOTMYDOTCNF}"
MYSQL_PROCESS_LIST="${default_MYSQL_PROCESS_LIST}"
USEINNODB="${default_USEINNODB}"
USEMYSQLPROCESSLIST="${default_USEMYSQLPROCESSLIST}"

Anyone wanting to use the mysql functionality would need to choose the desired option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants