| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| 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 22:47:46 |
| Message-ID: | 4B9EB912.9060000@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/15/10 8:41 AM, 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.
For my part, telling people that multi-thread pgbench doesn't work
correctly on systems which are not thread-safe seems perfectly OK.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-15 23:50:17 | Should we throw error when converting a nonexistent/ambiguous timestamp? |
| Previous Message | Jeff Davis | 2010-03-15 21:48:27 | Re: how to use advanced gist options |