| From: | Adrien NAYRAT <adrien(dot)nayrat(at)anayrat(dot)info> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Patrick Hemmer <postgresql(at)stormcloud9(dot)net> |
| Cc: | <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: performance statistics monitoring without spamming logs |
| Date: | 2018-11-22 08:20:19 |
| Message-ID: | 4f95cdc3-092f-1e7a-bb81-b628cfab20a2@anayrat.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 11/22/18 6:41 AM, Justin Pryzby wrote:
> and then probably look
> at the ratio of user CPU/clock time.
Maybe pg_stat_kcache could help you :
https://github.com/powa-team/pg_stat_kcache
https://rjuju.github.io/postgresql/2018/07/17/pg_stat_kcache-2-1-is-out.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jinhua Luo | 2018-11-22 08:31:14 | [Logical replication] Does the initial table data copy break the transactional replication? |
| Previous Message | Michael Paquier | 2018-11-22 07:53:21 | Re: [Todo item] Add entry creation timestamp column to pg_stat_replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2018-11-22 16:09:58 | Re: dsa_allocate() faliure |
| Previous Message | Justin Pryzby | 2018-11-22 05:41:15 | Re: performance statistics monitoring without spamming logs |