-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Do not enable read_uncommitted
by default
#12081
Labels
Milestone
Comments
I think we can close this - https://github.com/filecoin-project/lotus/pull/12090/files#diff-fe5e47a357d5465c3a2b1002977a53ad7c0990f76da22137417723577b87b19eL32 @rvagg made the change in pull #12090 |
That PR only updates events db pragma. right? |
yeah, only events sorry, we can follow up with the others as a separate PR |
rvagg
added a commit
that referenced
this issue
Jun 17, 2024
rvagg
added a commit
that referenced
this issue
Jun 17, 2024
rvagg
added a commit
that referenced
this issue
Jun 17, 2024
yes, it will, they'll all have the same pragma and read_uncommitted is gone |
rvagg
added a commit
that referenced
this issue
Jul 2, 2024
rvagg
added a commit
that referenced
this issue
Jul 15, 2024
ribasushi
pushed a commit
to ribasushi/ltsh
that referenced
this issue
Jul 16, 2024
ribasushi
pushed a commit
to ribasushi/ltsh
that referenced
this issue
Jul 16, 2024
ribasushi
pushed a commit
to ribasushi/ci-abusing-lotus-fork
that referenced
this issue
Jul 17, 2024
ribasushi
pushed a commit
to ribasushi/ltsh
that referenced
this issue
Jul 24, 2024
ribasushi
pushed a commit
to ribasushi/ci-abusing-lotus-fork
that referenced
this issue
Jul 24, 2024
ribasushi
pushed a commit
to ribasushi/ci-abusing-lotus-fork
that referenced
this issue
Aug 17, 2024
ribasushi
pushed a commit
to ribasushi/ci-abusing-lotus-fork
that referenced
this issue
Aug 20, 2024
ribasushi
pushed a commit
to ribasushi/ci-abusing-lotus-fork
that referenced
this issue
Aug 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
PRAGMA
for 3 databases across lotus repo enable uncommitted reads:lotus/chain/ethhashlookup/eth_transaction_hash_lookup.go
Line 25 in 395cdd7
lotus/chain/events/filter/index.go
Line 32 in 6bc04c8
lotus/chain/events/filter/index.go
Line 32 in 6bc04c8
This can have some performance gain but will cause all sorts of problems, specially in db interactions that require ACID properties where data consistency matters. Based on a quick look we do care about data consistency across all three places listed above. Therefore, I recommend against performing dirty reads.
The text was updated successfully, but these errors were encountered: