-
Notifications
You must be signed in to change notification settings - Fork 912
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
Purge channels from the DB after they have been irrevocably committed #740
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Christian Decker <[email protected]>
Signed-off-by: Christian Decker <[email protected]>
cdecker
force-pushed
the
forget-channels
branch
from
January 23, 2018 15:00
09c537f
to
ccdad10
Compare
rustyrussell
approved these changes
Jan 25, 2018
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 12, 2020
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 12, 2020
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 12, 2020
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 12, 2020
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 12, 2020
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 12, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 12, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 13, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 13, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 13, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 16, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 19, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
m-schmoock
added a commit
to m-schmoock/lightning
that referenced
this pull request
Mar 19, 2020
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
cdecker
pushed a commit
that referenced
this pull request
Mar 19, 2020
Changelog-Fixed: Use lightning-rfc #740 feespike margin factor of 2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This may cause the lingering
onchaind_mutual
channels in #721. Channels didn't get removed from the DB even though they were removed in memory. Alternatively we could mark the channels as resolved by setting their status to something that we ignore when loading.Dropping the channels cascades to remove all dependent tables, so this suffices to clear everything.