Fix worker-thread and linkage crashes#190
Open
estebanzimanyi wants to merge 1 commit into
Open
Conversation
estebanzimanyi
changed the base branch from
fix/bump-meos-pin
to
fix/bump-meos-pin-wasm-pgconfig
estebanzimanyi
changed the base branch from
fix/bump-meos-pin-wasm-pgconfig
to
fix/bump-meos-pin
estebanzimanyi
force-pushed
the
fix/bump-meos-pin
branch
4 times, most recently
from
fa2de57 to
17588c0
Compare
estebanzimanyi
force-pushed
the
fix/worker-thread-linkage-crashes
branch
2 times, most recently
from
a33f008 to
ec582fe
Compare
estebanzimanyi
force-pushed
the
fix/bump-meos-pin
branch
from
40bf218 to
45df2ad
Compare
estebanzimanyi
force-pushed
the
fix/worker-thread-linkage-crashes
branch
from
ec582fe to
f9e99dc
Compare
estebanzimanyi
force-pushed
the
fix/bump-meos-pin
branch
from
45df2ad to
2067f2a
Compare
estebanzimanyi
force-pushed
the
fix/worker-thread-linkage-crashes
branch
from
f9e99dc to
20328a7
Compare
estebanzimanyi
force-pushed
the
fix/bump-meos-pin
branch
from
2067f2a to
74ea89f
Compare
estebanzimanyi
force-pushed
the
fix/worker-thread-linkage-crashes
branch
2 times, most recently
from
6a4edaf to
dab415b
Compare
estebanzimanyi
force-pushed
the
fix/bump-meos-pin
branch
2 times, most recently
from
e12394e to
8d61366
Compare
estebanzimanyi
force-pushed
the
fix/worker-thread-linkage-crashes
branch
2 times, most recently
from
22d2966 to
db34f35
Compare
estebanzimanyi
force-pushed
the
fix/bump-meos-pin
branch
from
3e8da05 to
e5d0464
Compare
Scalar and cast bodies run MEOS on DuckDB TaskScheduler worker threads, which need a per-thread meos_initialize(); a thread-local guard in the scalar exec wrapper and a cast trampoline (RegisterMeosCastFunction) cover every entry point, so timestamp formatting no longer dereferences a NULL session_timezone. Per-type DuckDB callbacks and blob helpers have internal linkage and a single canonical blob round-trip (TemporalToBlob / BlobToTemporal) declared once in temporal/temporal_blob.hpp, so each function-pointer registration binds to its own body. (cherry picked from commit 7b99a0c)
estebanzimanyi
force-pushed
the
fix/worker-thread-linkage-crashes
branch
from
db34f35 to
a8d5194
Compare
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.
Scalar and cast bodies run MEOS on DuckDB TaskScheduler worker threads, which need a per-thread meos_initialize(); a thread-local guard in the scalar exec wrapper and a cast trampoline (RegisterMeosCastFunction) cover every entry point, so timestamp formatting no longer dereferences a NULL session_timezone. Per-type DuckDB callbacks and blob helpers have internal linkage and a single canonical blob round-trip (TemporalToBlob / BlobToTemporal) declared once in temporal/temporal_blob.hpp, so each function-pointer registration binds to its own body.