Hi Seongjun, > this patch does not change anything for them either way.
I tested the extension case with stderr logging and logging_collector=off. A small extension sets Extension/HarnessOuterWait, calls ereport(LOG), then keeps waiting. The observer samples only after ereport(LOG) returns: unpatched active | Extension | HarnessOuterWait v8 active | NULL | NULL So v8 clears the outer event after logging returns. It is not briefly masked; it remains lost. I think the new logging sites should preserve the old event, or this patch should wait for the general fix. The longjmp cleanup sites can use a separate reset helper. My AI harness tested v8 on master at c68cba09dd7f: cassert build, regression, isolation and relevant TAP tests passed. SysloggerWrite also worked as intended. I did not rerun Windows. This looks close. I think this edge case needs one more iteration before commit. Happy to retest. Thanks, Nik
