| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
| Date: | 2018-06-20 07:42:11 |
| Message-ID: | B8834F26-229F-4B0A-A06F-885795F005E1@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 20 Jun 2018, at 09:30, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> wrote:
>
> The pg_stat_statements contains the statistics of the queries that are cumulative.
> I find that any optimizations that are done to improve the performance of a query
> are not be visible clearly until the stats are reset. Currently there is a function to
> reset all the statistics, I find it will be useful if we a function that resets the stats of
> a single query, instead of reseting all the queries.
I’ve found myself wanting this in the past, so +1 on the idea.
> Attached is a simple patch with implementation. Comments?
From only skimming it, the patch seems to lack documentation updates to
doc/src/sgml/pgstatstatements.sgml.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-06-20 07:44:04 | Re: ToDo: show size of partitioned table |
| Previous Message | Haribabu Kommi | 2018-06-20 07:30:31 | New function pg_stat_statements_reset_query() to reset statistics of a specific query |