We use pgfouine (http://pgfouine.projects.postgresql.org/).
I currently have postgres log every query that takes longer than
100ms, roll the log files every 24 hours, and run pgfouine nightly. I
check it every couple of mornings and this gives me a pretty good
picture of who misbehaved over the l
Thanks for the reply.
Here is what I found about my problem. When i set the
log_min_duration_statement and in the moments when the server performance is
degrading I can see that almost all queries run very slowly (10-100 times
slower). At first I thought that there is exclusive lock on one of the
>>> On Thu, Sep 20, 2007 at 4:36 PM, in message
<[EMAIL PROTECTED]>, "Kamen Stanev"
<[EMAIL PROTECTED]> wrote:
>
> Is there a way to find which query is doing large io operations and/or which
> is using cached data and which is reading from disk.
A big part of your cache is normally in the OS,
Hi everybody,
Is there a way to find which query is doing large io operations and/or which
is using cached data and which is reading from disk. I need to see this on a
production server to localize a slow and resource eating query. The
pg_statio* tables are very handy, but don't help me at all in