Bug #114156 | Contribution by Tencent: fts_sync_commit is not crash safe | ||
---|---|---|---|
Submitted: | 28 Feb 2024 11:52 | Modified: | 1 Apr 2024 20:34 |
Reporter: | Yin Peng (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: FULLTEXT search | Severity: | S3 (Non-critical) |
Version: | 8.0.36 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | Contribution |
[28 Feb 2024 11:52]
Yin Peng
[28 Feb 2024 11:53]
Yin Peng
Use the same trx_t object for 'fts_sql_commit' and 'fts_cmp_set_sync_doc_id' in function 'in function 'fts_sync_commit'. (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: patch.txt (text/plain), 3.04 KiB.
[28 Feb 2024 12:01]
MySQL Verification Team
Hello yin peng, Thank you for the report and contribution. regards, Umesh
[1 Apr 2024 20:34]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Server 8.0.37 and 8.4.0 releases, and here's the proposed changelog entry from the documentation team: Some FTS operations on tables with FTS indexes could have caused inconsistent results. For example, if the server terminated while synchronizing the FTS cache or when synchronization occurred concurrently with another FTS operation. Our thanks to Yin Peng and the Tencent team for the contribution. Thank you for the bug report.
[6 Jun 2024 8:34]
Edward Gilmore
Posted by developer: Bug reopened by merge info, no change to release note.