-
Notifications
You must be signed in to change notification settings - Fork 322
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.
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
chore: compact status tables before proceeding with migration #2688
Conversation
95cdfcd
to
a48c1ab
Compare
a48c1ab
to
8ca7b37
Compare
Codecov ReportBase: 46.63% // Head: 46.84% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2688 +/- ##
==========================================
+ Coverage 46.63% 46.84% +0.20%
==========================================
Files 297 298 +1
Lines 48696 48749 +53
==========================================
+ Hits 22711 22836 +125
+ Misses 24557 24482 -75
- Partials 1428 1431 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
8ca7b37
to
446523b
Compare
43822d6
to
a9c24c3
Compare
0d89d50
to
2647a06
Compare
8892629
to
51a6134
Compare
51a6134
to
ce3066c
Compare
ce3066c
to
ed67cd2
Compare
e4e0623
to
2160cf7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A comment posted. Please take a look.
Description
Cleaning up the status table(delete all but the latest status per job) before proceeding with migration.
The DSs this is done to, are selected via analyzer estimates(
pg_class.reltuples
) and based on existing thresholds.This is once again repeated before the tables are backup, just to ensure that there's only one status per job in the uploaded file.
Moved migration related logic to
jobsdb/migration.go
.Notion Ticket
Perform compaction on the rightmost dataset during migration if necessary
Security