From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Marinos J. Yannikos <mjy@geizhals.at>
Cc: pgsql-performance@postgresql.org
Subject: Re: GiST indexes and concurrency (tsearch2)
Date: Thu, 03 Feb 2005 09:28:52 +0000
Message-ID: <4201EED4.60606@familyhealth.com.au> (raw)
In-Reply-To: <4201AEB1.4000504@geizhals.at>
References: <4201AEB1.4000504@geizhals.at>
> It seems to be a big problem with tsearch2, when multiple clients are
> hammering the db (we have a quad opteron box here that stays 75% idle
> despite an apachebench with concurrency 10 stressing the php script that
> uses tsearch2, with practically no disk accesses)
Concurrency with READs is fine - but you can only have one WRITE going
at once.
Chris
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: chriskl@familyhealth.com.au, mjy@geizhals.at
Subject: Re: GiST indexes and concurrency (tsearch2)
In-Reply-To: <4201EED4.60606@familyhealth.com.au>
* 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