Bruce Momjian wrote: <blockquote cite="mid:200912110055.nBB0tFE29298@momjian.us" type="cite"><pre wrap="">Peter
Eisentrautwrote: </pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">if i remove the -j option then it
runswithout a problem </pre></blockquote><pre wrap="">Possibly related to the incomplete removal of the
enable-thread-safety
option that I just posted about. </pre></blockquote><pre wrap="">
I thought about that but I can't figure out how that would affect
pgbench. </pre></blockquote> The "-j" option is the recent addition to pgbench that causes it to launch multiple client
threadswhen enabled, each handling a subset of the transactions. There's blocks of codes in pgbench.c now that depend
onhaving sane values for thread safety in libpq. That it may be detecting the wrong thing and operating in an unsafe
wayafter the recent change is what Peter's suggesting. This is good, actually, because I don't think we had many
client-sidethread-safety tests floating around to catch problems in this area before.<br /><br /><pre
class="moz-signature"cols="72">--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
<a class="moz-txt-link-abbreviated" href="mailto:greg@2ndQuadrant.com">greg@2ndQuadrant.com</a> <a
class="moz-txt-link-abbreviated"href="http://www.2ndQuadrant.com">www.2ndQuadrant.com</a>
</pre>