my-ship-it commented on issue #1708: URL: https://github.com/apache/cloudberry/issues/1708#issuecomment-4385461621
Thanks for the update @adnanhamdussalam — that confirms it's a real SIGSEGV (not OOM, not a cancel). The single frame you pasted is just the signal handler itself, so we still can't see where it actually crashed. Two things would let us pin this down: **1. The full segment stack (frames 2 through ~12).** The PANIC line you found is on one specific segment — please open that segment's log directly (not the coordinator's). The CSV log truncates long fields, so prefer the plain `.log` file: ```bash # on the segment host where the PANIC happened grep -A 25 'received signal SIGSEGV' /data/primary/gpseg*/pg_log/*.log | head -120 ``` Frame 1 (`StandardHandlerForSigillSigsegvSigbus_OnMainThread`) is the handler. Frames 2+ are what we need — that's the actual crash site. If you have core dumps enabled, even better: ```bash gdb \$GPHOME/bin/postgres <core-file> -batch -ex 'bt full' ``` **2. One quick retry with the legacy planner.** ```sql SET optimizer = off; -- then run the same CREATE TEMP TABLE AS ... query ``` If it stops crashing → the bug is in ORCA. If it still crashes → the bug is in the executor and ORCA is off the table. Either result narrows the search a lot. Once we have the stack frames + the optimizer-off result, we can match this against fixes that landed after the 2.1.0-incubating tag. Your build is at \`bdf90c5\` (the release commit itself); main is several hundred commits ahead and includes a few SIGSEGV / ORCA fixes that are candidates here, but I don't want to point at a specific one until the stack tells us where we actually are. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
