Re: seems like a bug in pgbench -R
Tomas Vondra <tomas.vondra@2ndquadrant.com>
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-03-15T22:05:28Z
Lists: pgsql-hackers
On 3/15/19 5:16 PM, Fabien COELHO wrote: > >>> echo 'select 1' > select.sql >>> >>> while /bin/true; do >>> pgbench -n -f select.sql -R 1000 -j 8 -c 8 -T 1 > /dev/null 2>&1; >>> date; >>> done; >> >> Indeed. I'll look at it over the weekend. >> >>> So I guess this is a bug in 12788ae49e1933f463bc59a6efe46c4a01701b76, or >>> one of the other commits touching this part of the code. > > I could not reproduce this issue on head, but I confirm on 11.2. > AFAICS on head it's fixed by 3bac77c48f166b9024a5ead984df73347466ae12 regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix possible lockup in pgbench with -R.
- e991b6cce3f2 11.5 landed
- 46c193213adb 10.10 landed
-
Rework the pgbench state machine code for clarity
- 3bac77c48f16 12.0 cited
-
Refactor script execution state machine in pgbench.
- 12788ae49e19 10.0 cited