> Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
> > BTW, running long benchmark using pgbench on BIG tables easily causes
> > an integer overflow error in following SQLs:
> > I'm inclined to change abalance, tbalance and bbalance column to
> > BIGINT to avoid the error. Opinion?
> No. The problem is that the deltas are invariably positive, which is
> not realistic (at least *my* bank balance isn't uniformly increasing :-().
> I think the correct fix is just to tweak the range of the randomly
> distributed deltas to be plus and minus not always plus.
I have never thought about it. Seems nice idea. Thanks.
> If you change to bigint then post-change results won't be strictly
> comparable to pre-change results because of the difference in execution
Yes, that was my concerning too.
SRA OSS, Inc. Japan
In response to
pgsql-hackers by date
|Next:||From: Michael Glaesemann||Date: 2006-07-26 23:16:25|
|Subject: Re: GUC with units, details|
|Previous:||From: Andrew Dunstan||Date: 2006-07-26 22:26:11|
|Subject: Re: [PATCHES] [PATCH] Provide 8-byte transaction IDs to|