Re: A failure in prepared_xacts test - Mailing list pgsql-hackers

From Tom Lane
Subject Re: A failure in prepared_xacts test
Date
Msg-id 1068977.1714367460@sss.pgh.pa.us
Whole thread Raw
In response to Re: A failure in prepared_xacts test  (Michael Paquier <michael@paquier.xyz>)
Responses Re: A failure in prepared_xacts test
Re: A failure in prepared_xacts test
Re: A failure in prepared_xacts test
Re: A failure in prepared_xacts test
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> If you grep the source tree, you'd notice that a prepared transaction
> named gxid only exists in the 2PC tests of ECPG, in
> src/interfaces/ecpg/test/sql/twophase.pgc.  So the origin of the
> failure comes from a race condition due to test parallelization,
> because the scan of pg_prepared_xacts affects all databases with
> installcheck, and in your case it means that the scan of
> pg_prepared_xacts was running in parallel of the ECPG tests with an
> installcheck.

Up to now, we've only worried about whether tests running in parallel
within a single test suite can interact.  It's quite scary to think
that the meson setup has expanded the possibility of interactions
to our entire source tree.  Maybe that was a bad idea and we should
fix the meson infrastructure to not do that.  I fear that otherwise,
we'll get bit regularly by very-low-probability bugs of this kind.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: pg_input_error_info doc 2 exampled crammed together
Next
From: Corey Huinker
Date:
Subject: Re: documentation structure