-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Open
Labels
BugA problem or regression with an existing featureA problem or regression with an existing featureaffects/5.2This issue or pull-request affects 5.2.x releases (and maybe further versions)This issue or pull-request affects 5.2.x releases (and maybe further versions)affects/6.0This issue or pull-request affects 6.0.x releases (and maybe further versions)This issue or pull-request affects 6.0.x releases (and maybe further versions)confirmed/5.2This issue is confirmed to be reproduced on 5.2 at the time this label was setThis issue is confirmed to be reproduced on 5.2 at the time this label was setconfirmed/6.0This issue is confirmed to be reproduced on 6.0 at the time this label was setThis issue is confirmed to be reproduced on 6.0 at the time this label was set
Description
Describe the bug
When Show only active is checked then some statements are not displayed despite being active.
This happens because the STATE column in information_schema.PROCESSLIST is empty.
Statement where I've seen this happen are UPDATE and SET, but only some UPDATE statements. For some the Status is Updating.
Makes me think it could also be a bug with MariaDB …
How to Reproduce
I executed a bunch of update statements of this form, they never have a state set.
UPDATE `t` SET `updated` = `updated`, `coord` = ST_PointFromWKB(IF(`x` = 0, POINT(0, 0), POINT(`x` / 1e5, `y` / 1e5)), 4326) WHERE id BETWEEN 1062900001 AND 1063000000;Expected behavior
These statements are active and should not be hidden in this case.
Database Server
MariaDB 11.4.7
phpMyAdmin version
5.2.3, 6.0.0
Additional context
State is empty ---, if Show only active were selected, they are not shown.

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugA problem or regression with an existing featureA problem or regression with an existing featureaffects/5.2This issue or pull-request affects 5.2.x releases (and maybe further versions)This issue or pull-request affects 5.2.x releases (and maybe further versions)affects/6.0This issue or pull-request affects 6.0.x releases (and maybe further versions)This issue or pull-request affects 6.0.x releases (and maybe further versions)confirmed/5.2This issue is confirmed to be reproduced on 5.2 at the time this label was setThis issue is confirmed to be reproduced on 5.2 at the time this label was setconfirmed/6.0This issue is confirmed to be reproduced on 6.0 at the time this label was setThis issue is confirmed to be reproduced on 6.0 at the time this label was set