| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: pg_stat_statements |
| Date: | 2008-06-15 02:14:10 |
| Message-ID: | 200806142214.10835.xzilla@users.sourceforge.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday 13 June 2008 12:58:22 Josh Berkus wrote:
> ITAGAKI Takahiro wrote:
> > Hello,
> >
> > Postgres 8.4 has pg_stat_user_functions view to track number of calls of
> > stored functions and time spent in them. Then, I'm thinking a "sql
> > statement" version of similar view -- pg_stat_statements.
>
> I can see how this would be useful, but I can also see that it could be a
> huge performance burden when activated. So it couldn't be part of the
> standard statistics collection.
>
A lower overhead way to get at this type of information is to quantize dtrace
results over a specific period of time. Much nicer than doing the whole
logging/analyze piece.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-06-15 03:09:30 | Re: [HACKERS] SSL configure patch |
| Previous Message | Alvaro Herrera | 2008-06-14 22:35:44 | Re: log_filename() |