public inbox for [email protected]
help / color / mirror / Atom feedFrom: Steeve Boulanger <[email protected]>
To: Adrian Klaver <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Database stats ( pg_stat_database.stats_reset ) get reset on daily basis - why?
Date: Sat, 23 Nov 2024 07:06:30 -0600
Message-ID: <CAAiSvx9CangeS_yZ6RLXsXHBZSKmuRvrcB39DNSB_Ler3=OhTw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAiSvx8_Z6QGey92dC+6Yona18KDMLWinfR5LOJsMgj-42XJtg@mail.gmail.com>
<[email protected]>
<CAAiSvx_vsiCmL3gBj+1hRpMxo=nOc3HUa+VaGO9_GfOXDWCsrQ@mail.gmail.com>
<[email protected]>
<CAAiSvx-pwz562KrTPdayK+qqRm9DxbrU1r9_Qkpm5BLh-1G+pA@mail.gmail.com>
<[email protected]>
<CAAiSvx_ZtM72ZO=uq56X=iJ=a17KcgB=07c5abyFnQ8vAses0Q@mail.gmail.com>
<[email protected]>
<CAAiSvx-JPJCGc_VR+YrUNo75pb0yrmB8Ng3zBOCf+Mksdo5JYg@mail.gmail.com>
<[email protected]>
> What is the [2] referring to?
Number of the log line for each session or process, starting at 1
> My guess is the difference in time it takes to log the action and set
> the log timestamp. Whereas the stats_reset value is the timestamp when
> the stats system actually did the reset.
Very plausible. I thought the same too.
> The above is some garden variety select?
Not 100% sure what the expression "garden variety select" means lol, but
I'll take a guess that it means an "select from an in-house application"
.. and yes it is.
-Steeve
On Fri, Nov 22, 2024 at 11:18 AM Adrian Klaver <[email protected]>
wrote:
> On 11/21/24 15:50, Steeve Boulanger wrote:
> > > 1) Do the 77 share some trait the other 80 don't.
> >
> > No pattern found yet .. but still verifying a few things
> >
> > > 2) Do the OS system logs reveal anything?
> >
> > Nothing found in syslog
> >
> > > 3) What was happening in the databases just prior to the time the
> stats
> > reset?
> >
> > Here's an example (log extracts) for a stats reset occurrence:
> >
> > select datname, stats_reset, now()-stats_reset as since_reset
> > from pg_stat_database
> > where ( now()-stats_reset ) < interval '1 day'
> > order by 3 limit 1;
> >
> > datname | stats_reset | since_reset
> > ----------------+-------------------------------+-----------------
> > MyDB | *2024-11-21 13:48:34.332*785+00 | 00:00:22.266304
> >
> > <--LOGS-->
> > 2024-11-21 13:48:34.324 UTC pid=[322035][2] db=[MyDB] usr=[user1]
> > client=[host1] app=[[unknown]]LOG: connection authorized: user=user1
> > database=MyDB applicatio
> > n_name=app1 <..>
>
> What is the [2] referring to?
>
> >
> > <.. no calls at "2024-11-21 13:48:34.332" - WHY?? ..>
>
> My guess is the difference in time it takes to log the action and set
> the log timestamp. Whereas the stats_reset value is the timestamp when
> the stats system actually did the reset.
>
> >
> > 2024-11-21 13:48:34.336 UTC pid=[322035][3] db=[MyDB] usr=[user1]
> > client=[host1] app=[app1]LOG: duration: 1.071 ms parse <unnamed>:
> > SELECT <..>
>
> The above is some garden variety select?
>
>
>
> --
> Adrian Klaver
> [email protected]
>
>
view thread (15+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Database stats ( pg_stat_database.stats_reset ) get reset on daily basis - why?
In-Reply-To: <CAAiSvx9CangeS_yZ6RLXsXHBZSKmuRvrcB39DNSB_Ler3=OhTw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox