fix: indexer crash-loops on "relation already exists" during self-healing - #26
Open
gamandeepsingh wants to merge 1 commit into
Open
Conversation
…cond snapshot run
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
fix: indexer crash-loops on "relation already exists" during self-healing
create_accounts_to_delete_table.sqlran a plainCREATE UNLOGGED TABLE accounts_to_delete AS SELECT ...with no preceding drop. On the first snapshot run the table is created and never cleaned up within the process. When self-healing triggers a second snapshot run, the sameCREATEfires again →relation "accounts_to_delete" already exists→ panic → process exits → full re-bootstrap → next gap → same panic. Unbreakable crash loop.Fixed by prepending
DROP TABLE IF EXISTS accounts_to_deleteto the SQL, mirroring the existing cleanup pattern used bytemp_closed_accounts.Closes #18