From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Weird test mixup
In-reply-to: <10fd6cdd-c5d9-46fe-9fa1-7e661191309e@iki.fi>
References: <10fd6cdd-c5d9-46fe-9fa1-7e661191309e@iki.fi>
Comments: In-reply-to Heikki Linnakangas <hlinnaka@iki.fi>
	message dated "Thu, 14 Mar 2024 23:23:46 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2387220.1710454778.1@sss.pgh.pa.us>
Date: Thu, 14 Mar 2024 18:19:38 -0400
Message-ID: <2387221.1710454778@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2387221.1710454778%40sss.pgh.pa.us>
Precedence: bulk

Heikki Linnakangas <hlinnaka@iki.fi> writes:
> Somehow the 'gin-leave-leaf-split-incomplete' injection point was active 
> in the 'intarray' test. That makes no sense. That injection point is 
> only used by the test in src/test/modules/gin/. Perhaps that ran at the 
> same time as the intarray test? But they run in separate instances, with 
> different data directories.

Do they?  It'd be fairly easy to explain this if these things were
being run in "installcheck" style.  I'm not sure about CI, but from
memory, the buildfarm does use installcheck for some things.

I wonder if it'd be wise to adjust the injection point stuff so that
it's active in only the specific database the injection point was
activated in.

			regards, tom lane