Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query
От | Amit Kapila |
---|---|
Тема | Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query |
Дата | |
Msg-id | CAA4eK1J+x6gUbiBHAFab_ctNjWgr6x_tVZnD_tXkQn8m-GevVQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query (Haribabu Kommi <kommi.haribabu@gmail.com>) |
Ответы |
Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query
|
Список | pgsql-hackers |
On Tue, Nov 13, 2018 at 11:32 AM Haribabu Kommi <kommi.haribabu@gmail.com> wrote: > > On Mon, Nov 12, 2018 at 6:34 PM Amit Kapila <amit.kapila16@gmail.com> wrote: >> > I can revert it back to void, >> > >> >> +1, as we don't see any good reason to break backward compatibility. > > > Thanks for the review. > Attached the updated patch with return type as void. > With this patch, we are intending to remove the entries matching userid, dbid, queryid from hash table (pgss_hash), but the contents of the file ( pgss_query_texts.stat) will remain unchanged unless all of the entries are removed from hash table. This appears fine to me, especially because there is no easy way to remove the contents from the file. Does anybody see any problem with this behavior? -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: