Migrating a larger routing node from bbolt to PostgreSQL – a cautionary tale:
Ran into multiple failures during the migration with lndinit, followed by repeated PostgreSQL crashes. At one point, I almost gave up and cried. 😅
Now, PostgreSQL demands a full 16 GB of RAM, the CPU load sits at 30% across 6 cores, and I’m stuck with an 11 GB decayedlogdb_kv table that refuses to shrink – no matter what I try and the lnd machine needs to run with 24GB of RAM and also 3 Force Closures... Not what I wanted...
Lesson learned: maybe wait a bit longer before jumping on the PG train for larger routing nodes. 🤣
Amboss Space
⚡blitz⚡ - 028268...5049a2 - Amboss Space
⚡blitz⚡ - 028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2 - 48 channels - capacity 669,746,898 sats - Bitcoin Mainnet - Ambo...

