| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CPU time for pg_stat_statement |
| Date: | 2022-05-21 09:21:18 |
| Message-ID: | 20220521092118.c6fy5xyfsdn23ftb@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Sat, May 21, 2022 at 12:21:49AM +0300, Michail Nikolaev wrote:
>
> > This might be interesting:
> > https://github.com/powa-team/pg_stat_kcache
>
> Oh, nice, looks like it could help me to reduce CPU and test my
> assumption (using exec_user_time and exec_system_time).
>
> BWT, do you know why extension is not in standard contrib (looks mature)?
Because contrib isn't meant to eventually contain all possible extensions.
There is an official postgres extension network, and also community deb/rpm
repositories that are intended to handle postgres extensibility, and this
extension is available on all of that, same as a lot of other extensions, which
are at least as mature.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-05-21 09:57:10 | Re: PG15 beta1 fix pg_stat_statements view document |
| Previous Message | Sergei Kornilov | 2022-05-21 08:55:27 | Re:Remove an undefined function CalculateMaxmumSafeLSN |