| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| 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 15:40:31 |
| Message-ID: | 25309.1297870831@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Greg Smith <greg(at)2ndquadrant(dot)com> writes:
> 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.
FWIW, I think that bug report is effectively complaining that if you use
both drand48 and erand48, the former can impact the latter. If you use
only erand48, I don't see that there's any problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-02-16 15:40:41 | Re: Sync Rep for 2011CF1 |
| Previous Message | Robert Haas | 2011-02-16 15:38:43 | Re: multiset patch review |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2011-02-16 15:43:06 | Re: high user cpu, massive SELECTs, no io waiting problem |
| Previous Message | Justin Pitts | 2011-02-16 15:04:42 | Re: high user cpu, massive SELECTs, no io waiting problem |