You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue, but I cannot find a discussion tab for this project so I will ask my question here.
I am interested to perform a chantools dropchannelgraph but for a postgres-backed lnd. Is there any way to do this? I tried browsing through the postgres db especially the channeldb_kv to see if I can understand the contents but it is just a key-value table with binary (not human readable) data in the key and value columns.
If you can share maybe a SQL delete statement that I can run to get a similar effect to chantools dropchannelgraph it would be appreciated. Thanks.
The text was updated successfully, but these errors were encountered:
There is no easy way to do this yet. Dropping the channel graph does mean removing certain top-level KV buckets (which could be done with an SQL query). But to get the node working again, the node's own channels need to be re-inserted into the graph afterwards, otherwise things won't work properly. And that can only be done with the custom business logic implemented in chantools. So I'll need to add the ability for chantools to connect to a remote Postgres DB to perform the operation. But I don't think I'll have time to do that any time soon...
This is not an issue, but I cannot find a discussion tab for this project so I will ask my question here.
I am interested to perform a
chantools dropchannelgraph
but for a postgres-backed lnd. Is there any way to do this? I tried browsing through the postgres db especially thechanneldb_kv
to see if I can understand the contents but it is just a key-value table with binary (not human readable) data in thekey
andvalue
columns.If you can share maybe a SQL delete statement that I can run to get a similar effect to
chantools dropchannelgraph
it would be appreciated. Thanks.The text was updated successfully, but these errors were encountered: