navidrome/db
Deluan f4effde18e fix(pglite): resend a request the backend produced no output for
Three times during a scan on a real library, a new pool connection's
first query got no bytes back at all, which the previous commit turned
from a hang into an error. A run always emits at least a completion, so
no output means the packet was not run; the bridge now hands it over
again (twice at most) and logs it.
2026-09-04 23:32:29 -04:00
..
migrations perf(pglite): artist stats as hash joins, one statement for a full refresh; bigint library size 2026-09-04 23:23:50 -04:00
pglite fix(pglite): resend a request the backend produced no output for 2026-09-04 23:32:29 -04:00
backup.go feat(pglite): run Navidrome on the embedded PostgreSQL end to end 2026-09-04 20:41:52 -04:00
backup_test.go chore(deps): upgrade to Go 1.27 (#5990) 2026-08-30 12:43:15 -04:00
db.go feat(pglite): run Navidrome on the embedded PostgreSQL end to end 2026-09-04 20:41:52 -04:00
db_test.go feat(bfr): Big Refactor: new scanner, lots of new fields and tags, improvements and DB schema changes (#2709) 2025-02-19 20:35:17 -05:00
export_test.go perf(db): keep query planner statistics trustworthy with full ANALYZE (#5740) 2026-07-13 12:04:29 -04:00
optimize.go feat(pglite): run Navidrome on the embedded PostgreSQL end to end 2026-09-04 20:41:52 -04:00
optimize_test.go perf(db): keep query planner statistics trustworthy with full ANALYZE (#5740) 2026-07-13 12:04:29 -04:00