Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: handle FULLTEXT indexes specially in physical backup/restore #170

Closed
tanmoysrt opened this issue Feb 17, 2025 · 1 comment
Closed

feat: handle FULLTEXT indexes specially in physical backup/restore #170

tanmoysrt opened this issue Feb 17, 2025 · 1 comment
Assignees
@tanmoysrt

Comments

@tanmoysrt
Copy link
Member

https://dev.mysql.com/doc/refman/8.4/en/innodb-table-import.html#innodb-table-import-example
Image

After restoring, need to check indexes if they are corrupted, in case of corruption need to rebuild.

P.S: In frappe apps, the FULLTEXT indexes are on myisam tables.
@tanmoysrt tanmoysrt self-assigned this Feb 17, 2025
@tanmoysrt
Copy link
Member Author

fixed in #172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tanmoysrt tanmoysrt

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tanmoysrt