My experience is that any querry takes nearly all CPU. If you manage
to create
querry which takes minutes you have to wait. I do not know how much
of that
time is due to PostgreSQL and to OOo.
Hmm, when using pgAdmin or NetBeans I can do something else even
within the frontend while the query runs. When using Base I can still
type quite comfortably *outside* of OO while a query runs (although
the fan runs at full speed), but not inside.
I guess I am luckier than you with system balance, I wouldn't actually
know how to control the priority of postgres over other activities.
Best
Rainer
On 28.11.2008, at 13:42, Juraj Trenkler wrote:
Dňa Pi 28. November 2008 Rainer Schuetz napísal:
Thank you for your reaction, juraj. Does the SDBC-driver already
support OO3? I should have added OO3 as criteria as well (OO-Aqua-
build,Leopard,OO3,Postgres 8.3,JDBC).
I usually use the latest OOo builds with SDBC driver without problem.
I also consider the multi-threading issue quite serious. Complex
queries can take a long time, from whichever frontend. So my second
question would be: if one runs a query that (rightfully so :)) does
take a long time to finish, how much of OO is blocked during the wait
time?
My experience is that any querry takes nearly all CPU. If you manage
to create
querry which takes minutes you have to wait. I do not know how much
of that
time is due to PostgreSQL and to OOo.
juraj
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
