The threading bug appears when a duration is set for pgbench tests.<br /> Instead of a duration, if a number of xacts
isset, this error doesn't happen.<br /><br /> If i understood the problem well, when the alarm signal comes, all the
threadshave to disconnect even the ones looking for a setshell parameter at this moment, creating the thread error:<br
/>setshell: error getting parameter<br /> Client 0 aborted in state 1. Execution of meta-command failed.<br /><br /> I
amtrying to find an elegant way to solve this, but I can't figure out yet how to deal with this error as it looks
tricky.<br/>
