Re: Ragged latency log data in multi-threaded pgbench - Mailing list pgsql-hackers

From Takahiro Itagaki
Subject Re: Ragged latency log data in multi-threaded pgbench
Date
Msg-id 20100316120914.9C28.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: Ragged latency log data in multi-threaded pgbench  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Ragged latency log data in multi-threaded pgbench
List pgsql-hackers
Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp> wrote:

> > >   2. Use per-thread log files.
> > >      File names would be "pgbench_log.<main-process-id>.<thread-id>".

Here is a patch to implement per-thread log files for pgbench -l.

The log filenames are "pgbench_log.<main-process-id>.<thread-serial-number>"
for each thread, but the first thread (including single-threaded) still uses
"pgbench_log.<main-process-id>" for the name because of compatibility.

Example:
  $ pgbench -c16 -j4 -l
  $ ls
  pgbench_log.2196  pgbench_log.2196.1  pgbench_log.2196.2  pgbench_log.2196.3

Comments and suggenstions welcome.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center


Attachment

pgsql-hackers by date:

Previous
From: Takahiro Itagaki
Date:
Subject: Re: Ragged latency log data in multi-threaded pgbench
Next
From: Domenico Rotiroti
Date:
Subject: [RFC] Comments on PostPic project - Repost