What the developer wrote
Authored by AbelLykens
docs: update sql migration guide
What changed, and why it matters
This commit only updates a documentation file (docs/db_migration_guide.md) to explain when and how SQL migration steps are automatically applied. It adds three lines of clarifying text about log messages users will see. There is no code change and no security relevance.
No action required; this is a documentation clarification with no security implications.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds documentation-only guidance stating that SQL migration steps are automatically applied on LND restart after step 1 completes and db.use-native-sql=true is set, and that log lines from the SQLD subsystem indicate migration progress. No executable code, configuration defaults, or security-sensitive behavior is modified.
Changed components
docs/db_migration_guide.mdInspect captured patch +3 / −0
diff --git a/docs/db_migration_guide.md b/docs/db_migration_guide.md
index 2979996..e973adb 100644
--- a/docs/db_migration_guide.md
+++ b/docs/db_migration_guide.md
@@ -127,6 +127,9 @@ This will mitigate the poor Postgres performance on kvdb.
This stage unlocks true SQL performance by restructuring data into relational tables. Migration is **per-subsystem** and **incremental**.
+The migration steps are automatically applied when LND is restarted after step 1 was successfully completed and the config value db.use-native-sql=true is set.
+You will see log lines from the `SQLD` subsystem about the migration, such as `Starting migration of invoices from KV to SQL`.
+
### Subsystem Readiness
| Subsystem | Relational Backend | Migration Script | Status |
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.