Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chantools for postgres #53

Open
hazrulnizam opened this issue Dec 14, 2022 · 2 comments · May be fixed by #167
Open

Chantools for postgres #53

hazrulnizam opened this issue Dec 14, 2022 · 2 comments · May be fixed by #167

Comments

@hazrulnizam
Copy link

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.

@guggero
Copy link
Member

guggero commented Jan 3, 2023

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...

@SeverinAlexB
Copy link

+1 for general postgres support

@ziggie1984 ziggie1984 linked a pull request Nov 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants