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

From Tom Lane
Subject Re: Should we add debug_parallel_query=regress to CI?
Date
Msg-id 313859.1741191586@sss.pgh.pa.us
Whole thread Raw
In response to Should we add debug_parallel_query=regress to CI?  (Andres Freund <andres@anarazel.de>)
Responses Re: Should we add debug_parallel_query=regress to CI?
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> 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?

Yeah, it certainly seems like a test coverage gap.  However, we seem to
be moving towards a situation where each type of CI run is a special
snowflake that differs in multiple dimensions from other types.
That might make it difficult to figure out which dimension is
responsible for a particular failure.

(OTOH, the same can be said of the buildfarm, and we've survived
regardless.  So maybe I'm worried over nothing.)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Isaac Morland
Date:
Subject: Re: Allow database owners to CREATE EVENT TRIGGER
Next
From: Nathan Bossart
Date:
Subject: Re: doc: expand note about pg_upgrade's --jobs option