From: Heikki Linnakangas <heikki.linnakangas@iki.fi>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix backstop in gin test if injection point is not reached
Date: Fri, 15 Mar 2024 15:56:09 +0000
Message-ID: <E1rl9uj-003wnG-27@gemulon.postgresql.org> (raw)
Fix backstop in gin test if injection point is not reached
Per Tom Lane's observation that the test got stuck in infinite loop if
the injection_points module was not loaded. It was supposed to give up
after 10000 iterations, but the backstop was broken.
Discussion: https://www.postgresql.org/message-id/2498595.1710511222%40sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/d802ff06d0216d59aab3ddba6cb158d1f4b014db
Modified Files
--------------
src/test/modules/gin/expected/gin_incomplete_splits.out | 5 +++--
src/test/modules/gin/sql/gin_incomplete_splits.sql | 5 +++--
2 files changed, 6 insertions(+), 4 deletions(-)
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: heikki.linnakangas@iki.fi, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix backstop in gin test if injection point is not reached
In-Reply-To: <E1rl9uj-003wnG-27@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