DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=timbira.com;
	h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User;
	b=SU5JmBfJosCi3XeoLNlOQ1/f0JRzMfTmmkwk1IjSYhVXj8vfqd0oindoDwWATPTkRkj/Hp3sCXIbXZ7E39QC8/mCSPqeMxcpo6noLSAP0pupGsflBulMBXTbYXU1DpfR;
Message-ID: <4D2A965A.3000603@timbira.com>
Date: Mon, 10 Jan 2011 02:17:14 -0300
From: Euler Taveira de Oliveira <euler@timbira.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.1.16) Gecko/20101227 Icedove/3.0.11
MIME-Version: 1.0
To: Greg Smith <greg@2ndquadrant.com>
CC: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: pgbench to the MAXINT
References: <4D27C4E5.5000609@2ndquadrant.com>
In-Reply-To: <4D27C4E5.5000609@2ndquadrant.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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/