[MDEV-16597] column "memory_used" of information_schema can't report usage over 2G Created: 2018-06-27 Updated: 2023-12-14 Resolved: 2023-12-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server |
| Affects Version/s: | 10.1.23 |
| Fix Version/s: | 10.2.1 |
| Type: | Bug | Priority: | Trivial |
| Reporter: | Rick Pizzi | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Description |
|
While troubleshooting a query using over 9G of memory I noticed that the column "memory_used" is an integer and doesn't hold sizes over 2G; it will report 2147483647. Although it is unlikely for queries to use such large amounts of memory, this column should be a bigint and not an int for those situations where the weird thing happens. |
| Comments |
| Comment by Dave Gosselin [ 2023-12-14 ] |
|
After a bit of investigation, git blame shows that this issue was fixed in git sha 2dee76f4359d7e making this ticket a duplicate of |