kevinveenbirkenbach/backup-docker-to-local
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

0 Releases 16 Tags

RSS Feed
  • v3.1.3 9dc57c3235
    Compare

    - Restore: the postgres dump replay now runs under *--single-transaction*,
    Some checks failed
    CI (make tests, stable, publish) / make test (push) Has been cancelled
    Details
    CI (make tests, stable, publish) / Mark stable + publish image (SemVer tags only) (push) Has been cancelled
    Details

    kevinveenbirkenbach released this 2026-07-20 18:01:26 +00:00 | 0 commits to main since this release

    so a concurrent writer on a live database can no longer interleave a row
    between the replay's table re-create and its COPY and trip a "duplicate
    key value violates unique constraint" abort under ON_ERROR_STOP. This is
    the discourse restore-drill race (mini_scheduler upserting
    scheduler_stats(id=1) mid-restore) that failed the whole restore. The
    --empty pre-clean stays multi-statement (\gexec, one DROP per
    statement) because a single DROP transaction exhausts
    max_locks_per_transaction on large schemas (e.g. gitlab).

    • Refactor: the --empty pre-clean SQL moves out of the inline Python
      string into src/baudolo/restore/db/empty_preclean.sql (loaded via
      dirname(file), declared as package-data so it ships in the wheel).
    • Tests: a unit test guards the single-transaction / multi-statement split
      (replay carries --single-transaction, pre-clean does not); a new e2e
      reproduces the live-writer race and asserts the restore survives it.
    Downloads