X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 2FEBA9DC816
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 20 Dec 2005 11:28:01 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 02462-03
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 20 Dec 2005 11:28:05 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id C94B39DC82D
	for <pgsql-performance@postgresql.org>;
	Tue, 20 Dec 2005 11:27:58 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jBKFS3X9029466;
	Tue, 20 Dec 2005 10:28:03 -0500 (EST)
To: Oleg Bartunov <oleg@sai.msu.su>
cc: Anjan Dave <adave@vantage.com>, Vivek Khera <vivek@khera.org>,
	Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: High context switches occurring 
In-reply-to: <Pine.GSO.4.63.0512201806170.13553@ra.sai.msu.su> 
References: 
 <4BAFBB6B9CC46F41B2AD7D9F4BBAF785098F14@vt-pe2550-001.vantage.vantage.com>
	<Pine.GSO.4.63.0512200822360.13553@ra.sai.msu.su>
	<28871.1135089690@sss.pgh.pa.us>
	<Pine.GSO.4.63.0512201806170.13553@ra.sai.msu.su>
Comments: In-reply-to Oleg Bartunov <oleg@sai.msu.su>
	message dated "Tue, 20 Dec 2005 18:18:20 +0300"
Date: Tue, 20 Dec 2005 10:28:03 -0500
Message-ID: <29465.1135092483@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.021 required=5 tests=[AWL=0.021]
X-Spam-Score: 0.021
X-Spam-Level: 
X-Archive-Number: 200512/496
X-Sequence-Number: 16317

Oleg Bartunov <oleg@sai.msu.su> writes:
> I still wondering with very poor performance of my server. Moving
> pgdata to RAID6 helped - about 600 tps. Then, I moved pg_xlog to separate
> disk and got strange error messages

> postgres@ptah:~$ time pgbench  -c 10  -t 3000 pgbench
> starting vacuum...end.
> Client 0 aborted in state 8: ERROR:  integer out of range
> Client 7 aborted in state 8: ERROR:  integer out of range

I've seen that too, after re-using an existing pgbench database enough
times.  I think that the way the test script is written, the adjustments
to the branch balances are always in the same direction, and so
eventually the fields overflow.  It's irrelevant to performance though.

			regards, tom lane