From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PERFORM] pgbench to the MAXINT |
Date: | 2011-02-16 13:15:41 |
Message-ID: | 4D5BCDFD.2010703@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Tom Lane wrote:
> I think that might be a good idea --- it'd reduce the cross-platform
> variability of the results quite a bit, I suspect. random() is not
> to be trusted everywhere, but I think erand48 is pretty much the same
> wherever it exists at all (and src/port/ provides it elsewhere).
>
Given that pgbench will run with threads in some multi-worker
configurations, after some more portability research I think odds are
good we'd get nailed by
http://sourceware.org/bugzilla/show_bug.cgi?id=10320 : "erand48
implementation not thread safe but POSIX says it should be". The AIX
docs have a similar warning on them, so who knows how many versions of
that library have the same issue.
Maybe we could make sure the one in src/port/ is thread safe and make
sure pgbench only uses it. This whole area continues to be messy enough
that I think the patch needs to brew for another CF before it will all
be sorted out properly. I'll mark it accordingly and can pick this back
up later.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Florian Pflug | 2011-02-16 13:36:49 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
Previous Message | Oliver Jowett | 2011-02-16 12:43:09 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
From | Date | Subject | |
---|---|---|---|
Next Message | Marti Raudsepp | 2011-02-16 13:44:06 | Re: high user cpu, massive SELECTs, no io waiting problem |
Previous Message | Greg Smith | 2011-02-16 07:33:22 | Re: high user cpu, massive SELECTs, no io waiting problem |