Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
MDEV-25674's Master_Retry_Count is an unsigned long, which is larger (in theory and Linux) than the int range of the info-reading API's init_intvar_from_file.
Its PR currently parses the number from a string itself.
For consistency and future-proofing, we should expand init_intvar_from_file's limit itself, at least to long long but ideally with an unsigned long long overload as well (as in MySQL's version).
We must assess if this change impacts other numeric fields.
It would be a positive impact if a previous field fell for this trap and was reading over-int values truncated or clamped, because that's a bug.
Attachments
Issue Links
- is caused by
-
MDEV-25674 No SQL variable for master_retry_count setting
-
- Closed
-
wlad I need Master_Retry_Count to be a long to match --master-retry-count. And I completely agree that both of them shouldn’t be variable {{ulong}}s.
That’s its own refactoring, though. This task is about making sure the info files are capable for larger-than-{{int}}s, be them {{long}}s or {{uint64_t}}s.