Re: Failure with pgbench and --disable-thread-safety in ~v16

2023-12-04 Thread Michael Paquier
On Mon, Dec 04, 2023 at 12:17:37PM +0100, Alvaro Herrera wrote: > So, the fix is just to remove the -j2 in the command line. I'll do that > in a jiffy. There's no other test that uses -j, except the one > specifically designed to test threads. Thanks for the quick fix. -- Michael signature.asc

Re: Failure with pgbench and --disable-thread-safety in ~v16

2023-12-04 Thread Alvaro Herrera
On 2023-Dec-04, Michael Paquier wrote: > While running some tests for 8984480b545d, I have noticed that the TAP > tests of pgbench fail when ~16 is compiled with > --disable-thread-safety: > [16:51:10.467](0.004s) not ok 227 - working \startpipeline with serializable > status (got 1 vs expected 0

Re: Failure with pgbench and --disable-thread-safety in ~v16

2023-12-04 Thread Alvaro Herrera
On 2023-Dec-04, Michael Paquier wrote: > While running some tests for 8984480b545d, I have noticed that the TAP > tests of pgbench fail when ~16 is compiled with > --disable-thread-safety: > [16:51:10.467](0.004s) not ok 227 - working \startpipeline with serializable > status (got 1 vs expected 0