docs(issues): close EPIC #1525 persistence overhaul#1725
Merged
josecelano merged 1 commit intotorrust:developfrom May 1, 2026
Merged
docs(issues): close EPIC #1525 persistence overhaul#1725josecelano merged 1 commit intotorrust:developfrom
josecelano merged 1 commit intotorrust:developfrom
Conversation
Close EPIC torrust#1525 by moving the EPIC issue document and the final PostgreSQL sub-issue document to docs/issues/closed after finishing the incremental implementation plan. History: - The EPIC started months ago when we identified that adding PostgreSQL support was not straightforward with the previous persistence crate and required migration to sqlx. - DamnCrab opened PR torrust#1684, followed by PR torrust#1695 after review feedback. - Additional reviewer guidance was provided through PR torrust#1700 to help address change requests. - The final implementation was completed through the incremental plan documented in issue comment #4294475557 on issue torrust#1525. - The tracker now supports PostgreSQL. Ideas initially introduced in DamnCrab's PRs and retained in the final implementation: - Matrix DB compatibility script to validate tracker compatibility across database versions. - End-to-end tracker tests using a real BitTorrent client (containerized qBittorrent). - Basic database benchmarking to compare persistence performance before/after migration to sqlx and across database engines. Thanks to DamnCrab for valuable contributions and ideas that improved the final result. Co-authored-by: DamnCrab <42539593+DamnCrab@users.noreply.github.com>
josecelano
force-pushed
the
1525-close-epic-overhaul-persistence
branch
from
327a5cc to
9101e76
Compare
This was referenced May 1, 2026
Member
Author
|
ACK 9101e76 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1725 +/- ##
========================================
Coverage 79.73% 79.73%
========================================
Files 354 354
Lines 25597 25597
Branches 25597 25597
========================================
+ Hits 20409 20410 +1
Misses 4958 4958
+ Partials 230 229 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR closes the EPIC by moving completed issue documents into the closed issues folder:
docs/issues/1525-overhaul-persistence.md->docs/issues/closed/1525-overhaul-persistence.mddocs/issues/1723-1525-08-add-postgresql-driver.md->docs/issues/closed/1723-1525-08-add-postgresql-driver.mdEPIC History
The EPIC was created months ago when we identified that adding PostgreSQL support was not straightforward with the previous persistence crate. The work required migrating persistence to
sqlx.A community contributor, DamnCrab, opened PR #1684. After review feedback, they opened a follow-up PR #1695. To help address the requested changes, additional reviewer guidance and code was provided in PR #1700.
The final implementation was then completed through the incremental plan documented in issue comment:
That plan is now complete, and Torrust Tracker supports PostgreSQL.
Acknowledgement
Thanks to DamnCrab for valuable contributions and ideas retained in the final implementation:
sqlxmigration and across database engines.Closes #1525