Tom Lane <t...@sss.pgh.pa.us> wrote: > Takahiro Itagaki <itagaki.takah...@oss.ntt.co.jp> writes: > > Oops. There might be two solutions for the issue: > > 1. Use explicit locks. The lock primitive will be pthread_mutex for > > multi-threaded implementations or semaphore for multi-threaded ones. > > 2. Use per-thread log files. > > File names would be "pgbench_log.<main-process-id>.<thread-id>". > > I think #1 is out of the question, as the synchronization overhead will > do serious damage to the whole point of having a multithreaded pgbench. > #2 might be a reasonable idea.
Ok, I'll go for #2. Regards, --- Takahiro Itagaki NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
