-
Notifications
You must be signed in to change notification settings - Fork 70
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
Server crashes if parallel run "type_support" test #425
Labels
bug
Something isn't working
Comments
@saygoodbyye hi, can you provide commit hash was used for this bug? |
@mkaruza, I have pulled new changes and tried to execute new array_type_support test added in #282 like above. So I've got the same assert.
backtrace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007c0006c4526e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007c0006c288ff in __GI_abort () at ./stdlib/abort.c:79
#5 0x000060319379482a in ExceptionalCondition (conditionName=conditionName@entry=0x6031937f9470 "TransactionIdFollowsOrEquals(xid, TransactionXmin)", fileName=fileName@entry=0x60319388b068 "subtrans.c", lineNumber=lineNumber@entry=169) at assert.c:66
#6 0x00006031932f9579 in SubTransGetTopmostTransaction (xid=xid@entry=1018) at subtrans.c:169
#7 0x00006031937d77fb in XidInMVCCSnapshot (xid=1018, snapshot=snapshot@entry=0x603195051090) at snapmgr.c:1929
#8 0x00006031932afa0e in HeapTupleSatisfiesMVCC (htup=<optimized out>, snapshot=0x603195051090, buffer=2219) at heapam_visibility.c:1071
#9 0x00006031932b0d1a in HeapTupleSatisfiesVisibility (htup=<optimized out>, snapshot=<optimized out>, buffer=<optimized out>) at heapam_visibility.c:1772
#10 0x00007c00077c74db in pgduckdb::HeapReader::ReadPageTuples (this=0x7bfed0000f50, output=...) at /usr/include/c++/13/bits/unique_ptr.h:199
#11 0x00007c00077cb5ed in pgduckdb::PostgresSeqScanFunction::PostgresSeqScanFunc (context=..., data=..., output=...) at src/scan/postgres_seq_scan.cpp:101
#12 0x00007c00035bc49e in duckdb::PhysicalTableScan::GetData(duckdb::ExecutionContext&, duckdb::DataChunk&, duckdb::OperatorSourceInput&) const () from /tmp/pgsql/lib/libduckdb.so
#13 0x00007c0003760a0f in duckdb::PipelineExecutor::FetchFromSource(duckdb::DataChunk&) () from /tmp/pgsql/lib/libduckdb.so
#14 0x00007c000376bfe9 in duckdb::PipelineExecutor::Execute(unsigned long) () from /tmp/pgsql/lib/libduckdb.so
#15 0x00007c000376c352 in duckdb::PipelineTask::ExecuteTask(duckdb::TaskExecutionMode) () from /tmp/pgsql/lib/libduckdb.so
#16 0x00007c000376258d in duckdb::ExecutorTask::Execute(duckdb::TaskExecutionMode) () from /tmp/pgsql/lib/libduckdb.so
#17 0x00007c000376b04b in duckdb::TaskScheduler::ExecuteForever(std::atomic<bool>*) () from /tmp/pgsql/lib/libduckdb.so
#18 0x00007c00068ecdb4 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#19 0x00007c0006c9ca94 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:447
#20 0x00007c0006d29c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Moreover, I get warnings while building: src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<16> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:638:40: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
542 | auto &child_type = GetChildTypeRecursive(value.type());
| ^~~~~~~~~~
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<18> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:642:40: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<21> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:646:40: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<23> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:650:40: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<20> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:654:40: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<1043> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:661:43: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<1082> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:665:40: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<1114> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:669:45: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<700> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:673:42: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<701> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:677:42: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<1700> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:681:43: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable]
src/pgduckdb_types.cpp: In instantiation of ‘void pgduckdb::ConvertDuckToPostgresArray(TupleTableSlot*, duckdb::Value&, idx_t) [with OP = PODArray<PostgresOIDMapping<2950> >; TupleTableSlot = TupleTableSlot; idx_t = long unsigned int]’:
src/pgduckdb_types.cpp:685:40: required from here
src/pgduckdb_types.cpp:542:15: warning: unused variable ‘child_type’ [-Wunused-variable] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happens?
If we parallel run type_support test like below, server will crash
PostgreSQL build:
To Reproduce
Patch test/regression/schedule:
Then execute
regression.out:
backtrace:
OS:
Ubuntu 24.04
pg_duckdb Version:
main
Postgres Version:
REL_17_STABLE
Hardware:
No response
Full Name:
Egor Chindyaskin
Affiliation:
Postgres Professional
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a source build
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: