gregfelice commented on issue #2534: URL: https://github.com/apache/age/issues/2534#issuecomment-5369735203
Confirmed still crashing on current master (`4d9b2506`, AGE 1.8.0, PostgreSQL 18.4). Backtrace at the fault: ``` #0 0x00007fc0a258fc25 in create_cypher_merge_path (root=root@entry=0x55a1934c3e18, rel=rel@entry=0x55a1935b6350, custom_private=0x55a1935b22f0) at src/backend/optimizer/cypher_pathnode.c:200 #1 0x00007fc0a258fe78 in handle_cypher_merge_clause (rti=<optimized out>, rte=<optimized out>, root=0x55a1934c3e18, rel=0x55a1935b6350) at src/backend/optimizer/cypher_paths.c:229 #2 set_rel_pathlist (rti=<optimized out>, root=0x55a1934c3e18, rel=0x55a1935b6350, rte=0x55a1935b02f8) at src/backend/optimizer/cypher_paths.c:89 #3 set_rel_pathlist (root=0x55a1934c3e18, rel=0x55a1935b6350, rti=<optimized out>, rte=0x55a1935b02f8) at src/backend/optimizer/cypher_paths.c:64 ``` Note this crash is in the **planner**, not the executor — `create_cypher_merge_path` at src/backend/optimizer/cypher_pathnode.c:200, below `handle_cypher_merge_clause` and `set_rel_pathlist`. It never reaches execution, which makes it distinct from every other crash in the current backlog. 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]
