Re: Sample rate added to pg_stat_statements
От | Sami Imseih |
---|---|
Тема | Re: Sample rate added to pg_stat_statements |
Дата | |
Msg-id | CAA5RZ0tJjrX6YiQVDZCOA_BDMuhO-po_T8a3PmjxEEH_iL-qMg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Sample rate added to pg_stat_statements ("Andrey M. Borodin" <x4mmm@yandex-team.ru>) |
Ответы |
Re: Sample rate added to pg_stat_statements
|
Список | pgsql-hackers |
> To summarize the results of all benchmarks, I compiled them into a table: Thanks for compiling the benchmark data above. The main benefit of this patch will be to give the user a toggle if they are observing high spinlock contention due to pg_stat_statements which will likely occur on larger machines. I also did not see this thread [1] mentioned in the thread above, but one of the reasons pg_stat_statements.track_planning was turned off by default was due to the additional spinlock acquire to track the planning stats. Bringing this up as sample_rate might also be beneficial as well if a user decides to track planning. Regards, Sami [1] https://www.postgresql.org/message-id/flat/2895b53b033c47ccb22972b589050dd9@EX13D05UWC001.ant.amazon.com
В списке pgsql-hackers по дате отправления: