Noah Misch

Hello. Could you say more about what makes it hard for the application to know whether it has called start()? In other words, why would it be bad for your...

I'd accept such a PR. That said, how well would the following mitigate the trouble with using `pump`? ```perl eval { $h->pump }; die $@ if $@ and $@ ne...

Can you set `IPCRUNDEBUG=gory` in the environment and share the output from a failing run? I've been unable to reproduce this. I tried the test in a loop on a...

I plan to do it on 2025-08-14. Before that date, I'd welcome pull requests with accompanying `make check` and `make check_prove` results.

I can't reproduce that blame result: ```bash $ git blame origin/REL_18_STABLE src/backend/tcop/pquery.c | grep ') PortalRun(' Blaming lines: 100% (1799/1799), done. 3eea7a0c (Tom Lane 2024-12-09 14:38:19 -0500 685) PortalRun(Portal portal,...

See https://postgr.es/m/flat/[email protected] for an upstream decision involving the pglogical row_filter feature.

Applications needing Perl's interpretation can wrap the TAP source like in https://github.com/postgres/postgres/commit/22a4b10

Does the current test suite fail with debug_discard_caches=1, which removes the randomness? - If no: can you add a test that does fail under debug_discard_caches=1? - If yes, does this...

Got it. That's elegant. If you add those queries to the test suite in sql/, do they show wrong output without the rest of the change and correct output with...

Please do modify sql/ and expected/ with those test queries. Overall, the goal is for the test suite to contain unambiguous, future-proof instructions sufficient for a developer to reproduce the...