public inbox for [email protected]  
help / color / mirror / Atom feed
Reset date for Cumulative Statistics System when not in table
3+ messages / 2 participants
[nested] [flat]

* Reset date for Cumulative Statistics System when not in table
@ 2024-02-26 13:47  blockdump <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: blockdump @ 2024-02-26 13:47 UTC (permalink / raw)
  To: [email protected]

Hello,
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.

cheers
Guenter


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Reset date for Cumulative Statistics System when not in table
@ 2024-02-26 15:40  Laurenz Albe <[email protected]>
  parent: blockdump <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Laurenz Albe @ 2024-02-26 15:40 UTC (permalink / raw)
  To: blockdump <[email protected]>; [email protected]

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





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Reset date for Cumulative Statistics System when not in table
@ 2024-02-26 16:52  blockdump <[email protected]>
  parent: Laurenz Albe <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: blockdump @ 2024-02-26 16:52 UTC (permalink / raw)
  To: Laurenz Albe <[email protected]>; +Cc: [email protected]

Thank you so much for the info!

On Mon, Feb 26, 2024, 16:40 Laurenz Albe <[email protected]> wrote:

> 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
>


^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2024-02-26 16:52 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-02-26 13:47 Reset date for Cumulative Statistics System when not in table blockdump <[email protected]>
2024-02-26 15:40 ` Laurenz Albe <[email protected]>
2024-02-26 16:52   ` blockdump <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox