Comments on: Understand Your PostgreSQL Workloads Better with pg_stat_monitor https://www.percona.com/blog/understand-your-postgresql-workloads-better-with-pg_stat_monitor/ Thu, 01 Feb 2024 00:57:26 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Valerie Parham-Thompson https://www.percona.com/blog/understand-your-postgresql-workloads-better-with-pg_stat_monitor/#comment-10973708 Tue, 09 Aug 2022 19:18:02 +0000 https://www.percona.com/blog/?p=80890#comment-10973708 Hi, thanks for this tool! Did you get an idea of how much overhead this extension adds in your benchmarks?

]]> By: Kai Wagner https://www.percona.com/blog/understand-your-postgresql-workloads-better-with-pg_stat_monitor/#comment-10973617 Tue, 10 May 2022 14:48:52 +0000 https://www.percona.com/blog/?p=80890#comment-10973617 Hi Kirill,

as we speak, there is another fresh benchmark running against our GA release. As soon as those runs are through I’ll post an update.

]]> By: Matt Yonkovit (@MYonkovit) https://www.percona.com/blog/understand-your-postgresql-workloads-better-with-pg_stat_monitor/#comment-10973614 Fri, 06 May 2022 14:39:38 +0000 https://www.percona.com/blog/?p=80890#comment-10973614 It looks like the engineering team is engaged with you on Jira on this. Apologies for the delayed response. We are actively looking into it.

]]> By: Kirill Petrov https://www.percona.com/blog/understand-your-postgresql-workloads-better-with-pg_stat_monitor/#comment-10973613 Fri, 06 May 2022 04:53:42 +0000 https://www.percona.com/blog/?p=80890#comment-10973613 Hi, thanks for article, it looks really helpful for observability.

How much overhead pg_stat_monitor brings to execution times of queries?

]]> By: MichaelV https://www.percona.com/blog/understand-your-postgresql-workloads-better-with-pg_stat_monitor/#comment-10973611 Thu, 05 May 2022 16:21:44 +0000 https://www.percona.com/blog/?p=80890#comment-10973611 While this tool has high expectations in taking pg_stat_statements to the next level, support for this tool is not very good.
I created a critical bug with them 2 weeks ago that is not being addressed. It is just marked as TO BE DONE IN THE NEXT SPRINT. This bug will crash the PostgreSQL Instance –> https://jira.percona.com/browse/PG-382.

How can you all tout this is going GA soon when you have critical outstanding bugs like this that are not being addressed? Not very impressed with the support team for this product. I will caution my clients to not use it due to is critical instability.

]]>