Surfaced on branch feature/pgsql-native-backend-protocol (PR #5882) while implementing named portals. These gaps are NOT caused by the native extended-query or portals work — they were previously masked by a debug assert that crashed the process before the cases could run (fixed as a #3549 follow-up in 81f2b23), and the affected surface pre-dates the portals commits (verified by code-path analysis: the failing cases never touch the named-portal branches).
With pgsql-use_native_backend_protocol=true, pgsql-extended_query_protocol_test-t (currently harness-ignored in groups.json) has ~19 failing cases clustering in three areas:
- SET-tracked variables through the extended protocol — native mode does not replicate the libpq path's tracked-variable bookkeeping in some flows (cases around 298, 338, 341).
- locked_on_hostgroup interactions — the native epilogue for locked sessions is a minimal port (see 81f2b23); the fuller semantics need native equivalents (cases around 348, 353).
- Simple/extended query interleaving edge cases (cases around 354, 357).
Suggested approach: a dedicated hardening phase that (a) un-ignores the test for a native-mode run in CI once green, (b) works the three clusters in order. Case-by-case notes exist in the branch's task reports (P1/P2, 2026-07-08).
Surfaced on branch feature/pgsql-native-backend-protocol (PR #5882) while implementing named portals. These gaps are NOT caused by the native extended-query or portals work — they were previously masked by a debug assert that crashed the process before the cases could run (fixed as a #3549 follow-up in 81f2b23), and the affected surface pre-dates the portals commits (verified by code-path analysis: the failing cases never touch the named-portal branches).
With
pgsql-use_native_backend_protocol=true,pgsql-extended_query_protocol_test-t(currently harness-ignored in groups.json) has ~19 failing cases clustering in three areas:Suggested approach: a dedicated hardening phase that (a) un-ignores the test for a native-mode run in CI once green, (b) works the three clusters in order. Case-by-case notes exist in the branch's task reports (P1/P2, 2026-07-08).