From: Tom Lane <tgl@sss.pgh.pa.us>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Anjan Dave <adave@vantage.com>
Cc: Vivek Khera <vivek@khera.org>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: High context switches occurring
Date: Tue, 20 Dec 2005 10:28:03 -0500
Message-ID: <29465.1135092483@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, oleg@sai.msu.su, adave@vantage.com, vivek@khera.org
Subject: Re: High context switches occurring
In-Reply-To: <29465.1135092483@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox