Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query
От | Fujii Masao |
---|---|
Тема | Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query |
Дата | |
Msg-id | CAHGQGwE8Roydg-bVweK8GjpOipWh3rAAstMqoUfz7qBFrs8Tuw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query (Sergei Kornilov <sk@zsrv.org>) |
Ответы |
Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query
|
Список | pgsql-hackers |
On Fri, Jul 6, 2018 at 3:34 AM, Sergei Kornilov <sk@zsrv.org> wrote: > Hello > >> Currently pg_stat_statements_reset() and other stats reset functions like >> pg_stat_reset() can be executed only by superusers. >> But why did you allow pg_read_all_stats role to execute that function, >> by default? That change looks strange to me. > This is not behavior change, only fix documentation to current state. Commit https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=25fff40798fc4ac11a241bfd9ab0c45c085e2212creates 1.5 versionand grant execute to pg_read_all_stats Hmm... so pg_stat_statements_reset() is allowed to be executed by pg_read_all_stats role while other stats reset functions like pg_stat_reset() can be executed only by superusers. Which looks strange and inconsistent to me. Regards, -- Fujii Masao
В списке pgsql-hackers по дате отправления: