Details
-
Bug
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Duplicate
-
10.1.23
-
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.