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

Archive each table independently #606

Merged
merged 2 commits into from
Nov 13, 2024
Merged

Archive each table independently #606

merged 2 commits into from
Nov 13, 2024

Commits on Nov 12, 2024

  1. Archive each table independently 

    At the moment all operational tables are archived using a single
timestamp for the lower boundary, which either loses us data, if they're
uneven, or forces us to load duplicates to make sure we don't lose
anything. This is because some databases don't support atomic
modifications of multiple tables at once.

Work that around, by assigning separate time ranges to separate tables,
when dumping.
    @spbnick
    spbnick committed Nov 12, 2024
    Configuration menu
    Copy the full SHA
    1d6c607 View commit details
    Browse the repository at this point in the history

  2. tests: Wait longer for archival

    @spbnick
    spbnick committed Nov 12, 2024
    Configuration menu
    Copy the full SHA
    4ffbbb3 View commit details
    Browse the repository at this point in the history