pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marinos J. Yannikos <mjy@geizhals.at>
To: pgsql-performance@postgresql.org
Subject: GiST indexes and concurrency (tsearch2)
Date: Thu, 03 Feb 2005 05:55:13 +0100
Message-ID: <4201AEB1.4000504@geizhals.at> (raw)

Hi,

according to 
http://www.postgresql.org/docs/8.0/interactive/limitations.html , 
concurrent access to GiST indexes isn't possible at the moment. I 
haven't read the thesis mentioned there, but I presume that concurrent 
read access is also impossible. Is there any workaround for this, esp. 
if the index is usually only read and not written to?

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)

Regards,
  Marinos
-- 
Dipl.-Ing. Marinos Yannikos, CEO
Preisvergleich Internet Services AG
Obere Donaustraße 63/2, A-1020 Wien
Tel./Fax: (+431) 5811609-52/-55



view thread (17+ messages)  latest in thread

Message-ID: <4201AEB1.4000504@geizhals.at>
Permalink:  ../4201AEB1.4000504@geizhals.at/
Also on:    postgresql.org/message-id/4201AEB1.4000504@geizhals.at

 · 

reply

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: mjy@geizhals.at
  Subject: Re: GiST indexes and concurrency (tsearch2)
  In-Reply-To: <4201AEB1.4000504@geizhals.at>

* 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