cgosqlite: set SQLITE_TEMP_STORE=1 #102
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
|
What's with the compilation error? |
SQLITE_TEMP_STORE=1 allows PRAGMA temp_store = MEMORY, while keeping temporary files as the default behavior for temporary storage. This can be used to accelerate some migrations, when building an in-memory temporary btree to use in a later correlated subquery is faster than the query planner would normally do things, for example when optimizing locality or btree operation order.
raggi
force-pushed
the
raggi/enable-memory-temp
branch
from
3878690
to
5d04b87
Compare
It's on top of another patch, but didn't need to be, and is no longer. |
bradfitz
approved these changes
May 28, 2024
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.
SQLITE_TEMP_STORE=1 allows PRAGMA temp_store = MEMORY, while keeping temporary files as the default behavior for temporary storage.
This can be used to accelerate some migrations, when building an in-memory temporary btree to use in a later correlated subquery is faster than the query planner would normally do things, for example when optimizing locality or btree operation order.