Only update litestream_seq if size is below WAL header size #573
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
benbjohnson
force-pushed
the
422-fix-litestream-seq
branch
from
0606c81
to
80280fc
Compare
hifi
reviewed
Mar 6, 2024
| @@ -629,7 +629,7 @@ func (db *DB) acquireReadLock() error { | |||
| } | |||
|
|
|||
| // Execute read query to obtain read lock. | |||
| if _, err := tx.ExecContext(db.ctx, `SELECT COUNT(1) FROM _litestream_seq;`); err != nil { | |||
| if _, err := tx.ExecContext(context.Background(), `SELECT COUNT(1) FROM _litestream_seq;`); err != nil { | |||
There was a problem hiding this comment.
Why was this changed to background context? If the db context gets canceled we'd want the lock to fail fast as well, right?
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.
Previously, the
litestream_seqcould increment on aPASSIVEcheckpoint even if the WAL existed and did not need to be created. This caused a loop where the increment would trigger replication. This PR fixes this by only executing the increment if the WAL is below a size threshold.Fixes #422