From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marinos J. Yannikos <mjy@geizhals.at>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Cc: pgsql-performance@postgresql.org
Subject: Re: GiST indexes and concurrency (tsearch2)
Date: Thu, 03 Feb 2005 11:27:38 -0500
Message-ID: <16719.1107448058@sss.pgh.pa.us> (raw)
In-Reply-To: <4202053B.10207@geizhals.at>
References: <4201AEB1.4000504@geizhals.at>
<Pine.GSO.4.62.0502031255350.20328@ra.sai.msu.su>
<4202053B.10207@geizhals.at>
"Marinos J. Yannikos" <mjy@geizhals.at> writes:
> I can't seem to find out where the bottleneck is, but it doesn't seem to
> be CPU or disk. "top" shows that postgres processes are frequently in
> this state:
> 6701 postgres 16 0 204m 58m 56m S 9.3 0.2 0:06.96 semtimedo
> ^^^^^^^^^
What's the platform exactly (hardware and OS)?
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, mjy@geizhals.at, oleg@sai.msu.su
Subject: Re: GiST indexes and concurrency (tsearch2)
In-Reply-To: <16719.1107448058@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