| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "Campbell\, Lance" <lance(at)uiuc(dot)edu>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: SQL Monitoring |
| Date: | 2007-10-09 19:00:06 |
| Message-ID: | 878x6ccdvt.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
> Campbell, Lance wrote:
>> I have noticed a slight spike in the amount of CPU usage in the last few
>> weeks. I am sure it has to do with a change or two that was made to
>> some queries. What is the best way to log the SQL that is being
>> executed?
>
> Take a look at statement_timeout and log_statement configuration variables.
I suspect he meant log_min_duration_statement which lets you log only queries
which take too long and not statement_timeout which would actually kill your
query if it took too long.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radhika S | 2007-10-09 20:00:04 | Postgres running Very slowly |
| Previous Message | Heikki Linnakangas | 2007-10-09 15:07:59 | Re: SQL Monitoring |