| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Geek Matter <geekmatter(at)yahoo(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: profiling store procedure |
| Date: | 2012-03-23 08:04:01 |
| Message-ID: | CAL_0b1t9hY93ULtd2UMp7Z2Qu_Ch0pCR-C3PbyOHBcMarVYQPg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Mar 23, 2012 at 11:16 AM, Geek Matter <geekmatter(at)yahoo(dot)com> wrote:
> what tool is suitable for profiling store procedure in postgresql? sql
> server has sql profiles, how about postgresql?
You can use the pg_stat_statements
(http://www.postgresql.org/docs/9.1/interactive/pgstatstatements.html)
extension to do profiling. Turn track_utility to on to collect DDL and
set track to all to collect queries inside functions.
--
Sergey Konoplev
Blog: http://gray-hemp.blogspot.com
LinkedIn: http://ru.linkedin.com/in/grayhemp
JID/GTalk: gray(dot)ru(at)gmail(dot)com Skype: gray-hemp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2012-03-23 08:04:37 | Re: profiling store procedure |
| Previous Message | Heiko Wundram | 2012-03-23 07:34:48 | Re: [SOLVED] Very high memory usage on restoring dump (with plain pqsl) on pg 9.1.2 |