Commit a732d5e
committed
Bug#23540008 SAFE GUARD FOR CHARSET_INFO RETURNED FROM GET_CHARSET
When executing a SELECT from tables:
- performance_schema.events_statements_current
- performance_schema.events_statements_history
- performance_schema.events_statements_history_long
the code reads data that can be concurrently written to.
This race condition is expected (performance schema data buffers are lock
less), but the code is not robust enought.
In particular, the character set for the sql query text may be invalid.
Before this fix, this condition could cause a crash.
With this fix, reading an invalid character set will truncate the SQL
TEXT column.1 parent b079401 commit a732d5e
1 file changed
Lines changed: 11 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | | - | |
| 1 | + | |
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
| |||
340 | 340 | | |
341 | 341 | | |
342 | 342 | | |
343 | | - | |
| 343 | + | |
344 | 344 | | |
345 | | - | |
346 | | - | |
347 | | - | |
| 345 | + | |
| 346 | + | |
| 347 | + | |
| 348 | + | |
| 349 | + | |
| 350 | + | |
| 351 | + | |
| 352 | + | |
| 353 | + | |
348 | 354 | | |
349 | 355 | | |
350 | 356 | | |
| |||
0 commit comments