Skip to content

Commit b927793

Browse files
committed
docs: add release not for network separation safeguard
This is in particular important when running with a postgres backend. This only works if you run LND with the native sql flag but people should run it with this flag from 21 on anyways.
1 parent 5f43c1c commit b927793

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

docs/release-notes/release-notes-0.21.0.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -292,7 +292,15 @@
292292

293293
## Database
294294

295-
* Freeze the [graph SQL migration
295+
* [Prevent silent data corruption](https://github.com/lightningnetwork/lnd/pull/10684)
296+
when reusing the same database across different Bitcoin networks. On first
297+
startup the active network is persisted in a new `chain_params` table; on
298+
every subsequent restart lnd compares the stored value against the configured
299+
network and refuses to start if they differ, printing a clear error message
300+
with remediation steps. This safeguard applies to both the PostgreSQL and
301+
SQLite native-SQL backends when running with `--db.use-native-sql`.
302+
303+
* Freeze the [graph SQL migration
296304
code](https://github.com/lightningnetwork/lnd/pull/10338) to prevent the
297305
need for maintenance as the sqlc code evolves.
298306
* Prepare the graph DB for handling gossip V2

0 commit comments

Comments
 (0)