Re: Should we add debug_parallel_query=regress to CI?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Should we add debug_parallel_query=regress to CI?
Date: 2025-03-05 16:10:03
Message-ID: CAH2-Wznii5KoV9P+Yp-ScwfGp=XTxvbunxNSWiXcadGpQ0kuLQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 5, 2025 at 11:06 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> 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?

That would certainly be nice.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-03-05 16:13:00 Re: Enhance file_fdw to report processed and skipped tuples in COPY progress
Previous Message Andres Freund 2025-03-05 16:06:10 Should we add debug_parallel_query=regress to CI?