Summary: | db_revs 210600001 can take a long time | ||
---|---|---|---|
Product: | Koha | Reporter: | Magnus Enger <magnus> |
Component: | Database | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | a.roussos, emmi.takkinen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Magnus Enger
2023-01-25 07:24:40 UTC
If I have understood correctly, while DELETE is performed, deleted rows are still kept in case of a rollback or crash (could be something else, here are some reasons and tips I found: https://mariadb.com/kb/en/big-deletes/). We faced similar problem while archiving our action_logs table. We ended up renaming action_logs as work_action_logs and creating a new action_logs based on it. Then after moving everything in archive table and back to action_logs work_action_logs is dropped. Could something similar work here? Rename sessions table e.g. drop_sessions -> create new sessions table -> drop renamed table -> alter new sessions table. |