gregfelice commented on issue #2537: URL: https://github.com/apache/age/issues/2537#issuecomment-5369735420
Confirmed still crashing on current master (`4d9b2506`, AGE 1.8.0, PostgreSQL 18.4). Backtrace at the fault: ``` #0 0x00007fc0a258ae15 in apply_update_list (node=node@entry=0x55a1935f0ac8, set_info=0x55a1935f0cf8) at src/backend/executor/cypher_set.c:420 #1 0x00007fc0a258bb9c in process_update_list (node=0x55a1935f0ac8) at src/backend/executor/cypher_set.c:866 #2 exec_cypher_set (node=0x55a1935f0ac8) at src/backend/executor/cypher_set.c:930 #3 0x000055a181ffd032 in ?? () ``` This faults in `apply_update_list` at src/backend/executor/cypher_set.c:420, below `process_update_list` (:866) and `exec_cypher_set` (:930) — the SET executor. Distinct from the `create_vertex` group, though the query shape mixes SET, DELETE, CREATE and MERGE in one statement. For context: I triaged the current fuzz-report backlog against master today. There are six *distinct* crash sites in it, not one — the largest group is five issues (#2501, #2508, #2527, #2530, #2535) that all share a single NULL dereference in `create_vertex`, written up in #2535. **This issue is not part of that group**; it is its own defect and needs its own fix. -- 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]
