| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | dangal <danielito(dot)gallo(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: pg_stat_bgwriter |
| Date: | 2019-10-14 22:16:02 |
| Message-ID: | 20191014221602.GL3599@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Oct 14, 2019 at 08:18:47PM +0200, Tomas Vondra wrote:
> Note: FWIW, a single snapshot of pg_stats* may be misleading, because
> it's cumulative, so it's not clear how accurately it reflects current
> state. Next time take two snapshots and subtract them.
For bonus points, capture it with timestamp and make RRD graphs.
I took me awhile to get around to following this advice, but now I have 12+
months of history at 5 minute granularity across all our customers, and I've
used my own implementation to track down inefficient queries being run
periodically from cron, and notice other radical changes in writes/reads
I recall seeing that the pgCluu project does this.
http://pgcluu.darold.net/
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-10-15 00:39:35 | Re: pg_stat_bgwriter |
| Previous Message | dangal | 2019-10-14 20:12:43 | Re: pg_stat_bgwriter |