| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Ragged latency log data in multi-threaded pgbench |
| Date: | 2010-03-15 15:58:15 |
| Message-ID: | 4B9E5917.4070607@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Smith wrote:
> Just noticed a problem popping up sometimes with the new
> multi-threaded pgbench. This is on a Linux RPM build (the alpha4 set)
> compiled with '--disable-thread-safety'. Still trying to nail down
> whether that's a requirement for this problem to appear or not. I did
> most of my review of this feature with it turned on, and haven't been
> seeing this problem on other systems that are thread safe. Not sure
> yet if that's cause and effect or coincidence yet.
>
>
We had to turn handsprings to prevent this sort of effect with the
logging collector, which was a requirement of being able to implement
CSV logging sanely. So I'm not surprised by this report.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-15 16:06:19 | Re: Ragged latency log data in multi-threaded pgbench |
| Previous Message | Joe Conway | 2010-03-15 15:49:50 | Re: walreceiver is uninterruptible on win32 |