| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | blockdump <blockdump13(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reset date for Cumulative Statistics System when not in table |
| Date: | 2024-02-26 15:40:53 |
| Message-ID: | 0491db9ee6796afacb53a52c43e9f4905e49a188.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Mon, 2024-02-26 at 14:47 +0100, blockdump wrote:
> I am new to Postgres and started reading about the The Cumulative Statistics System.
> https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STATIO-ALL-TABLES-VIEW
>
> When I came across pg_statio_all_tables I was wondering what is the reference date for the
> counters like (heap_blks_read, heap_blks_hit ... ) This table does not have a stats_reset column like others.
> So are this numbers accumulating from the creation of the table or since the startup of the cluster ?
>
> Maybe someone can drop me a line.
Statistics survive a restart, but not a crash, so the statistics are
collected since the table was created, the latest crash happened or the
statistics were reset; whatever happened last.
Unfurtunately there is no way to find out the time when that happened.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | blockdump | 2024-02-26 16:52:24 | Re: Reset date for Cumulative Statistics System when not in table |
| Previous Message | blockdump | 2024-02-26 13:47:38 | Reset date for Cumulative Statistics System when not in table |