From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: pgbench to the MAXINT |
Date: | 2011-01-10 05:17:14 |
Message-ID: | 4D2A965A.3000603@timbira.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Em 07-01-2011 22:59, Greg Smith escreveu:
> setrandom: invalid maximum number -2147467296
>
It is failing at atoi() circa pgbench.c:1036. But it just the first one. There
are some variables and constants that need to be converted to int64 and some
functions that must speak 64-bit such as getrand(). Are you working on a patch?
> It doesn't throw any error during the initialization step, neither via
> client or database logs, even though it doesn't do anything whatsoever.
> It just turns into the quickest pgbench init ever. That's the exact
> threshold, because this works:
>
AFAICS that is because atoi() is so fragile.
> So where we're at now is that the maximum database pgbench can create is
> a scale of 21474.
>
That's because 21475 * 100,000 > INT_MAX. We must provide an alternative to
atoi() that deals with 64-bit integers.
--
Euler Taveira de Oliveira
http://www.timbira.com/
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2011-01-10 05:19:02 | Re: hstore ?& operator versus mathematics |
Previous Message | Robert Haas | 2011-01-10 01:35:41 | Re: GIN indexscans versus equality selectivity estimation |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-01-10 08:25:23 | Re: pgbench to the MAXINT |
Previous Message | Dimitri Fontaine | 2011-01-09 13:58:14 | Re: MySQL HandlerSocket - Is this possible in PG? |