Rename index for faster database restore #455
Merged
floatingghost
merged 2 commits from ilja/akkoma:rename_index_for_faster_restore
into develop
3 months ago
Loading…
Reference in new issue
There is no content yet.
Delete Branch 'ilja/akkoma:rename_index_for_faster_restore'
Deleting a branch is permanent. It CANNOT be undone. Continue?
fix #440
I manually changed the index name. On a 10G dump it took ~30min to restore with this rename. I don't know exactly how long it took without renaming the index, but I tried and cancelled the operation after it was already stuck on the problematic index for over 1h.
I also saw that the renamed index is indeed the very first index that's being restored (and before the "problematic" activities_visibility_index).
Renaming the index:
It's a bit dirty because we go away from naming conventions, but if it works, I think it's worth it.
[1]
Excerpt from the output from restoring the DB. We see the renamed index being the first index restored (2nd output line), and the "problematic" visibility index only later (last output line of this excerpt).
WIP: Rename index for faster database restoreto Rename index for faster database restore 4 months ago32658dafd6
to972a73aea9
4 months ago972a73aea9
to3b634dcbe7
3 months agohehe that's a nice index name
aa
looks good, thankies
f7211459ef
into develop 3 months agof7211459ef
.