What changed, and why it matters
This commit only adds a few lines to the release notes document describing unrelated SQL payment store improvements. It is a documentation-only change with no code modifications.
No action required; this is a documentation-only release-notes update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates docs/release-notes/release-notes-0.21.0.md to summarize PR #10535 (SQL payment store improvements: indexes, query performance, timestamp handling, omit_hops option, SQLite cache size). No source code, build scripts, tests, or configuration files were changed.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +6 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 6363068..0b421e7 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -258,6 +258,12 @@
migration](https://github.com/lightningnetwork/lnd/pull/10485) with
comprehensive tests. The migration is currently dev-only, compiled behind
the `test_db_postgres`, `test_db_sqlite`, or `test_native_sql` build tags.
+ * Various [SQL payment store
+ improvements](https://github.com/lightningnetwork/lnd/pull/10535):
+ optimize schema indexes, improve query performance for payment filtering
+ and failed attempt cleanup, fix cross-database timestamp handling, add
+ `omit_hops` option to `ListPayments` to reduce response size, and increase
+ the default SQLite cache size.
## Code Health
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.