Re: pgsql: Prevent port collisions between concurrent TAP tests

2022-11-26 Thread Michael Paquier
On Sat, Nov 26, 2022 at 07:40:52AM -0500, Andrew Dunstan wrote: > Yes, good point. Will do. Thanks. -- Michael signature.asc Description: PGP signature

Re: pgsql: Prevent port collisions between concurrent TAP tests

2022-11-26 Thread Andrew Dunstan
On 2022-11-26 Sa 06:15, Michael Paquier wrote: > Hi Andrew, > > On Tue, Nov 22, 2022 at 03:56:43PM +, Andrew Dunstan wrote: >> Prevent port collisions between concurrent TAP tests >> >> Currently there is a race condition where if concurrent TAP tests both >> test that they can open a port th

Re: pgsql: Prevent port collisions between concurrent TAP tests

2022-11-26 Thread Michael Paquier
Hi Andrew, On Tue, Nov 22, 2022 at 03:56:43PM +, Andrew Dunstan wrote: > Prevent port collisions between concurrent TAP tests > > Currently there is a race condition where if concurrent TAP tests both > test that they can open a port they will assume that it is free and use > it, causing one

pgsql: Prevent port collisions between concurrent TAP tests

2022-11-22 Thread Andrew Dunstan
Prevent port collisions between concurrent TAP tests Currently there is a race condition where if concurrent TAP tests both test that they can open a port they will assume that it is free and use it, causing one of them to fail. To prevent this we record a reservation using an exclusive lock, and

pgsql: Prevent port collisions between concurrent TAP tests

2022-11-22 Thread Andrew Dunstan
Prevent port collisions between concurrent TAP tests Currently there is a race condition where if concurrent TAP tests both test that they can open a port they will assume that it is free and use it, causing one of them to fail. To prevent this we record a reservation using an exclusive lock, and

pgsql: Prevent port collisions between concurrent TAP tests

2022-11-22 Thread Andrew Dunstan
Prevent port collisions between concurrent TAP tests Currently there is a race condition where if concurrent TAP tests both test that they can open a port they will assume that it is free and use it, causing one of them to fail. To prevent this we record a reservation using an exclusive lock, and

pgsql: Prevent port collisions between concurrent TAP tests

2022-11-22 Thread Andrew Dunstan
Prevent port collisions between concurrent TAP tests Currently there is a race condition where if concurrent TAP tests both test that they can open a port they will assume that it is free and use it, causing one of them to fail. To prevent this we record a reservation using an exclusive lock, and

pgsql: Prevent port collisions between concurrent TAP tests

2022-11-22 Thread Andrew Dunstan
Prevent port collisions between concurrent TAP tests Currently there is a race condition where if concurrent TAP tests both test that they can open a port they will assume that it is free and use it, causing one of them to fail. To prevent this we record a reservation using an exclusive lock, and

pgsql: Prevent port collisions between concurrent TAP tests

2022-11-20 Thread Andrew Dunstan
Prevent port collisions between concurrent TAP tests Currently there is a race condition where if concurrent TAP tests both test that they can open a port they will assume that it is free and use it, causing one of them to fail. To prevent this we record a reservation using an exclusive lock, and