| From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
|---|---|
| To: | "Marinos J(dot) Yannikos" <mjy(at)geizhals(dot)at> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: GiST indexes and concurrency (tsearch2) |
| Date: | 2005-02-03 09:57:37 |
| Message-ID: | Pine.GSO.4.62.0502031255350.20328@ra.sai.msu.su |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 3 Feb 2005, Marinos J. Yannikos wrote:
> 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?
there are should no problem with READ access.
>
> 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)
I'm willing to see some details: version, query, explain analyze.
>
> Regards,
> Marinos
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2005-02-03 10:30:32 | Re: Bad query optimizer misestimation because of TOAST |
| Previous Message | Din Adrian | 2005-02-03 09:55:04 | Tunning postgresql on linux (fedora core 3) |