gregfelice commented on PR #2475: URL: https://github.com/apache/age/pull/2475#issuecomment-4983045806
Follow-up now that this is merged (thanks @MuhammadTahaNaveed) — flagging a release-branch gap. **The fix is on `master` (2e4b4ad9) but not on `release/PG18/1.8.0`.** That branch tip is still e43dc1a1, which predates this merge, so the staged `PG18/v1.8.0-rc0` artifacts do **not** contain the crash fix. As it stands, 1.8.0 would ship with a backend SIGSEGV that's already fixed on master. I verified the cherry-pick so the mechanics are a known quantity if you decide to respin: - `git cherry-pick 2e4b4ad9` onto `release/PG18/1.8.0` applies **cleanly** — no conflicts, exactly the 3 expected files (`cypher_delete.c`, `security.sql`, `security.out`). - Builds against PG18, and the **full 41-test regress suite passes** on the release branch with it applied — including `security`, which carries the DETACH-DELETE-under-RLS reproducer. So this is a clean cherry-pick + RC1 respin whenever you're ready. Your call as RM on timing; just didn't want the vote to go out against a branch that's missing a merged crash fix. (Same likely applies to the PG19 release branch — I only verified PG18.) -- 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]
