Closed aleszeleny closed 3 years ago
Hello,
I think that the root issue is that you didn't activate pg_stat_statements.track_planning, which isn't enabled by default.
The same option for pg_stat_kcache is indeed enabled by default, but the planning time time column displayed in the UI is the one retrieved from pg_stat_statements. pg_stat_kcache times are summed and displayed in the "CPU time repartition" graph, in the IO tab on the per-query page (I didn't have time yet to write the queries to display those graphs on the per-database and per-cluster pages unfortunately).
Hello,
I've put in the listing above pg_stat_kcache.track_planning
is enabled - otherwise, I won't be able to see plan times in select from pg_stat_kcache_detail - this was the method I've used to validate, that the planning time might be collected by powa-collector.
I agree, but as I said the plantime you're showing in the screenshot comes from pg_stat_statements.track_planning
, not pg_stat_kcache.track_planning
.
Hello, I'm sorry, my fault. I'll test enabling planner time on pg_stat_statememts
Thanks
Aleš Zelený
Dne pá 19. 2. 2021 18:10 uživatel Julien Rouhaud notifications@github.com napsal:
I agree, but as I said the plantime you're showing in the screenshot comes from pg_stat_statements.track_planning, not 'pg_stat_kcache.track_planning`.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/powa-team/powa-web/issues/131#issuecomment-782210408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AILJV7ZVB7C4PILGB5QDFTLS72LRJANCNFSM4X4OPAJA .
I'm sorry, you are absolutely right, once pg_stat_statements.track_planning
was enabled, it worked like a charm.
Kind regards Ales
Great, thanks for the confirmation!
I'm using the remote setup with powa-collector.![2021-02-19_14-54_powa_plamnning_time_is_missing](https://user-images.githubusercontent.com/35035903/108513094-647bf800-72c2-11eb-879b-0899e487263e.png)
I've used pg bench, but only created an ugly query to enforce some noticeable planning time. The monitored database instance and central powa database are the same versions.
The detail view itself nicely shows planning time, so might be a problem in the powa-web or collector. Hopefully, I've configured the whole stuff correctly since all other metrics are displayed as expected. Is there something I have to check before considering the issue as a bug? Thanks ales