From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Disable parallel query in psql error-with-FETCH_COUNT test.
Date: Sun, 07 Apr 2024 01:49:36 +0000
Message-ID: <E1rtHf5-000tle-LF@gemulon.postgresql.org> (raw)
Disable parallel query in psql error-with-FETCH_COUNT test.
The buildfarm members using debug_parallel_query = regress are mostly
unhappy with this test. I guess what is happening is that rows
generated by a parallel worker are buffered, and might or might not
get to the leader before the expected error occurs. We did not see
any variability in the old version of this test because each FETCH
would succeed or fail atomically, leading to a predictable number of
rows emitted before failure. I don't find this to be a bug, just
unspecified behavior, so let's disable parallel query for this one
test case to make the results stable.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/beb012b42f5c32f578661fc1b033ca25905b27d6
Modified Files
--------------
src/test/regress/expected/psql.out | 3 +++
src/test/regress/sql/psql.sql | 3 +++
2 files changed, 6 insertions(+)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Disable parallel query in psql error-with-FETCH_COUNT test.
In-Reply-To: <E1rtHf5-000tle-LF@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox