Re: Feature improvement for pg_stat_statements
От | Yuki Seino |
---|---|
Тема | Re: Feature improvement for pg_stat_statements |
Дата | |
Msg-id | 160284527026.1154.6227116286776459506.pgcf@coridan.postgresql.org обсуждение исходный текст |
Ответ на | Re: Feature improvement for pg_stat_statements (btnakamichin <btnakamichin@oss.nttdata.com>) |
Ответы |
Re: Feature improvement for pg_stat_statements
|
Список | pgsql-hackers |
The following review has been posted through the commitfest application: make installcheck-world: tested, passed Implements feature: tested, failed Spec compliant: tested, passed Documentation: tested, failed The patch applies cleanly and looks fine to me.I'm going to list a few points that I think need to be fixed. 1.There are unnecessary difference lines 89 in "pg_stat_statements.c". 2.It is confusing that the initial value of reset_time is the current date and time, so why not set it to null? 3.How about pg_stat_statements_reset_time creates a view? 4.How about counting the number of resets? 5."pgstatstatstatements.sgml" would need to include the function name in the following section. - these statistics, the module provides a view, <structname>pg_stat_statements</structname>, - and the utility functions <function>pg_stat_statements_reset</function> and - <function>pg_stat_statements</function>. These are not available globally but - can be enabled for a specific database with + these statistics, the module provides views, <structname>pg_stat_statements</structname> + and <structname>pg_stat_statements_ctl</structname>, + and the utility functions <function>pg_stat_statements_reset</function>, + <function>pg_stat_statements</function>, and <function>pg_stat_statements_reset_time</function>. + These are not available globally but can be enabled for a specific database with It would be nice to be able to keep the timing of resetting the userid, dbid and queryid as well, but I think the statusquo is appropriate for management in memory. The new status of this patch is: Waiting on Author
В списке pgsql-hackers по дате отправления: