| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | Anjan Dave <adave(at)vantage(dot)com>, Vivek Khera <vivek(at)khera(dot)org>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: High context switches occurring |
| Date: | 2005-12-20 15:28:03 |
| Message-ID: | 29465.1135092483@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Oleg Bartunov <oleg(at)sai(dot)msu(dot)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(at)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-12-20 15:48:08 | Re: Read only transactions - Commit or Rollback |
| Previous Message | David Lang | 2005-12-20 15:22:24 | Re: PostgreSQL and Ultrasparc T1 |