pgsql: Each worker thread will have its own log file in pgbench to avoid

From: itagaki(at)postgresql(dot)org (Takahiro Itagaki)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Each worker thread will have its own log file in pgbench to avoid
Date: 2010-03-23 01:29:22
Message-ID: 20100323012923.005347541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Each worker thread will have its own log file in pgbench to avoid interleaved
writes. The first worker still uses "pgbench_log.<pid>" for the name, but
additional workers use "pgbench_log.<pid>.<serial-number>" instead.

Reported by Greg Smith.

Modified Files:
--------------
pgsql/contrib/pgbench:
pgbench.c (r1.97 -> r1.98)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pgbench/pgbench.c?r1=1.97&r2=1.98)
pgsql/doc/src/sgml:
pgbench.sgml (r1.12 -> r1.13)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/pgbench.sgml?r1=1.12&r2=1.13)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2010-03-23 02:28:48 pgsql: Add back other xlog() function author names.
Previous Message Peter Eisentraut 2010-03-22 23:48:04 Re: Re: [COMMITTERS] pgsql: Prevent the injection of invalidly encoded strings by PL/Python