What changed, and why it matters
This commit only adds a line to the release notes describing a previously merged performance fix. It does not change any code, configuration, or behavior. The underlying change it documents replaced a slow database query with faster ones and removed redundant database indexes, which improves efficiency but is not a security patch.
No action needed for this commit. Review PR #10619 separately if a security assessment of the actual query optimization is desired.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to docs/release-notes/release-notes-0.21.0.md. It describes PR #10619, which replaced a catch-all GetInvoice query using OR $1 IS NULL predicates (causing full table scans) with three dedicated queries targeting uniquely-constrained columns, and removed four redundant indexes. No source code is modified in this commit.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +7 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 5c456d2..d6ecb37 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -149,6 +149,13 @@
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
+ 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
+ that duplicated UNIQUE constraints or were never used as query filters.
+
## Deprecations
### ⚠️ **Warning:** The deprecated fee rate option `--sat_per_byte` will be removed in release version **0.22**
Why this scored 16/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.