What the developer wrote
Authored by Elle Mouton
docs: add release notes
What changed, and why it matters
This commit only updates the release notes document for version 0.21.0. It adds a description of a performance improvement (asynchronous channel graph cache loading) and fixes minor formatting/spacing in existing notes. There are no code changes, no bug fixes, and no security-related content.
No security action needed. This is a documentation-only commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is limited to docs/release-notes/release-notes-0.21.0.md. It adds a bullet point describing PR #10065, which makes the channel graph cache populate asynchronously on startup, with reads falling back to the database until the cache is ready. It also removes extra spaces in two existing bullet points. No executable code is modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +9 / −2
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index c9d458d..87309d0 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -166,6 +166,13 @@
## Performance Improvements
+* Let the [channel graph cache be populated
+ asynchronously](https://github.com/lightningnetwork/lnd/pull/10065) on
+ startup. While the cache is being populated, the graph is still available for
+ queries, but all read queries will be served from the database until the cache
+ is fully populated. This new behaviour can be opted out of via the new
+ `--db.sync-graph-cache-load` option.
+
* [Replace the catch-all `FilterInvoices` SQL query with five focused,
index-friendly queries](https://github.com/lightningnetwork/lnd/pull/10601)
(`FetchPendingInvoices`, `FilterInvoicesBySettleIndex`,
@@ -176,11 +183,11 @@
only the parameters it actually needs and uses a direct `ORDER BY`, allowing
the planner to perform efficient index range scans on the invoice table.
-* [Fix full table scans on the HTLC settlement
+* [Fix full table scans on the HTLC settlement
hot path](https://github.com/lightningnetwork/lnd/pull/10619).
Replace the catch-all `GetInvoice` query (which used `OR $1 IS NULL`
predicates that forced full table scans) with three dedicated queries
- targeting uniquely-constrained columns. Also drop four redundant indexes
+ targeting uniquely-constrained columns. Also drop four redundant indexes
that duplicated UNIQUE constraints or were never used as query filters.
## Deprecations
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.