From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Steeve Boulanger <sboulanger29(at)gmail(dot)com> |
Cc: | Ray O'Donnell <ray(at)rodonnell(dot)ie>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Database stats ( pg_stat_database.stats_reset ) get reset on daily basis - why? |
Date: | 2024-11-24 00:28:28 |
Message-ID: | 017913c7-92d3-4967-bf78-2a4dbd193506@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/23/24 16:20, Steeve Boulanger wrote:
> Apologies for the late reply.
>
> > I'm guessing shutting down Netdata did not stop the resets?
>
> There was a hiccup yesterday, so I had to redo the test and wait until
> today to see if there were any stats resets ... and NONE today!!
>
> reset_status | cnt
> --------------------+-----
> reset before today | 100
> no reset | 57
> reset today | 0
Getting closer.
>
> This is quite interesting, and a little unexpected... but in order to
> confirm this theory, I have done the following just now:
>
> 1) Restart Netdata service
> 2) rename the "pg_stat_reset()" function , as you suggested in another
> post - very clever btw! :-)
Not sure who 'you' refers to, but just to be clear that was Greg Sabino
Mullane.
>
> Now let's wait until tomorrow to see if we have any stats reset and/or
> some relevant errors in the PG logs!
>
> Quick note: I did do a quick check in any user functions for any
> "pg_stat_reset" calls , but didn't find any. With that said, we have
> 150+ databases in our cluster, so perhaps I missed something. I also did
> a grep on the netdata directories, but nothing as well.
>
> -Steeve
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-11-24 02:04:03 | Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10 |
Previous Message | Steeve Boulanger | 2024-11-24 00:20:28 | Re: Database stats ( pg_stat_database.stats_reset ) get reset on daily basis - why? |