> kiki wrote:
>> The speed of the query is not a problem but the strange thing is the
>> processor load with postmaster when the query is executed.
>> I dont now how to reduce processor load.
>
> Did you try without the ORDER BY?
> Where are the execution plans?
Hello Herald,
the queried table is used for communication between server application and
web user interface.
When application detects an event it writes it down in table.
The web client checks every 10 second if something new is written in the
table.
Usually nothing new is written but the client h
Sorry, without LIMIT returns around 70 rows.
Tried to index date column and time column but the performance is pretty
much the same.
Everything is OK, I just dont understand way is this query burdening the
processor so much.
Regards,
Maja
> kiki wrote:
>> First I have
ing the process id for the where clause (where procpid = ).
>
> How often is the table being queried modified? Between the startup when
> the
> query is fast, and when it slows down, is there a lot of modification to
> its
> rows?
>
>
> On Fri, Sep 26, 2008 at 5:52 AM, Albe
Thank's for your response.
The situation is that the top result is when the server is already
exhibiting problems.
The number of rows returned by the query varies, right now is:
49 row(s)
Total runtime: 3,965.718 ms
The table currently has 971582 rows.
But the problem is that when database serv
Hello,
postmaster heavily loads processor. The database is accessed from java
aplication (with several threads), C applications and from PHP scripts.
It seems that one php script, called periodicaly, rises the load but the
script is very simple, something like this:
$var__base = new baza($dbhost
