Should we add debug_parallel_query=regress to CI? - Mailing list pgsql-hackers

Hi,

In https://postgr.es/m/CAH2-WzkYXSnM60ZNo-vQLxFoGzHLHFD0x%3DiPHF6VGxiZmWUuwQ%40mail.gmail.com
Peter wrote:

On 2025-03-05 09:37:05 -0500, Peter Geoghegan wrote:
> Committed just now. Thanks again.

But since had to revert, due to BF issues:

commit d00107cd63e780753aa25563fa37603369997d0c
Author: Peter Geoghegan <pg@bowt.ie>
Date:   2025-03-05 10:27:31 -0500

    Revert "Show index search count in EXPLAIN ANALYZE."

    This reverts commit 5ead85fbc81162ab1594f656b036a22e814f96b3.

    This commit shows test failures with debug_parallel_query=regress.  The
    underlying issue needs to be debugged, so revert for now.


Post-commit issues due to debug_parallel_query=regress seem rather common,
surely not helped by CI/cfbot not flagging them. I wonder if we ought to make
one of the CI tasks use debug_parallel_query=regress, to avoid that problem?

Greetings,

Andres