gregfelice commented on issue #2506: URL: https://github.com/apache/age/issues/2506#issuecomment-5369734951
Confirmed still crashing on current master (`4d9b2506`, AGE 1.8.0, PostgreSQL 18.4). Backtrace at the fault: ``` #0 0x000055a182307c64 in pg_detoast_datum () #1 0x00007fc0a258899a in create_vertex (css=css@entry=0x55a1935be290, node=0x55a1935beaa8, next=0x0, list=0x55a1935be618) at src/backend/executor/cypher_create.c:585 #2 0x00007fc0a25887fb in create_edge (css=0x55a1935be290, node=0x55a1935be688, prev_vertex_id=844424930131969, next=<optimized out>, list=<optimized out>) at src/backend/executor/cypher_create.c:386 #3 create_vertex (css=css@entry=0x55a1935be290, node=<optimized out>, next=<optimized out>, list=<optimized out>) at src/backend/executor/cypher_create.c:636 ``` This one faults inside `pg_detoast_datum` called from `create_vertex` at cypher_create.c:585, reached via `create_edge` (:386) — a different line and a different failure mode from the :526 group: a NULL relationship endpoint is being detoasted as if it were a real datum. 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]
