X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B8B268B9CE6 for ; Thu, 3 Feb 2005 09:30:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12367-10 for ; Thu, 3 Feb 2005 09:30:06 +0000 (GMT) Received: from server.cityscape3d.com (unknown [217.206.144.18]) by svr1.postgresql.org (Postfix) with ESMTP id F23408B9F30 for ; Thu, 3 Feb 2005 09:30:07 +0000 (GMT) Received: from [192.168.1.117] ([192.168.1.117]) by server.cityscape3d.com (8.12.11/8.11.6) with ESMTP id j1397vah032853; Thu, 3 Feb 2005 09:07:57 GMT (envelope-from chriskl@familyhealth.com.au) Received: from 127.0.0.1 (AVG SMTP 7.0.302 [265.8.4]); Thu, 03 Feb 2005 09:28:52 +0000 Message-ID: <4201EED4.60606@familyhealth.com.au> Date: Thu, 03 Feb 2005 09:28:52 +0000 From: Christopher Kings-Lynne User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Marinos J. Yannikos" Cc: pgsql-performance@postgresql.org Subject: Re: GiST indexes and concurrency (tsearch2) References: <4201AEB1.4000504@geizhals.at> In-Reply-To: <4201AEB1.4000504@geizhals.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.016 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/54 X-Sequence-Number: 10383 > 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