| Bug #110954 | DanglingFullTextIndex Query in Version Upgrade Pre Checks Performing Bad | ||
|---|---|---|---|
| Submitted: | 9 May 2023 2:49 | Modified: | 6 Jun 2023 15:45 |
| Reporter: | Anirudh Vasudevan | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | Shell Upgrade Checker | Severity: | S5 (Performance) |
| Version: | 8.0.33 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | DanglingFullTextIndex, Pre-UpgradeChecks, SlowQuery, subquery, Version Upgrade | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[9 May 2023 2:52]
Anirudh Vasudevan
[9 May 2023 2:52]
Anirudh Vasudevan
Suggested Query fix for finding dangling full text index references as part of Upgrade Pre-checks
Attachment: dangling FULLTEXT index - Suggested Fix.sql (application/octet-stream, text), 1.16 KiB.
