Re: Add session statistics to pg_stat_database
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Magnus Hagander <magnus@hagander.net>
Cc: Ahsan Hadi <ahsan.hadi@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>,
Soumyadeep Chakraborty <soumyadeep2007@gmail.com>, Masahiro Ikeda
<ikedamsh@oss.nttdata.com>, PostgreSQL Hackers
<pgsql-hackers@lists.postgresql.org>
Date: 2020-12-05T12:04:13Z
Lists: pgsql-hackers
Attachments
- 0001-Add-session-statistics-to-pg_stat_database.v8.patch (text/x-patch) patch v8-0001
On Fri, 2020-12-04 at 16:55 +0100, I wrote: > > > Basically, that would change pgStatSessionDisconnectedNormally into instead being an > > > enum of reasons, which could be normal disconnect, abnormal disconnect and admin. > > > And we'd track all those three as separate numbers in the stats file, meaning we could > > > then calculate the crash by subtracting all three from the total number of sessions? > > > > I think at least "closed by admin" might be interesting; I'll have a look. > > I don't think we have to specifically count "closed by normal disconnect", because > > that should be the rule and could be more or less deduced from the other numbers > > (with the uncertainty mentioned above). > > I am considering the cases > > 1) client just went away (currently "aborted") > 2) death by FATAL error > 3) killed by the administrator (or shutdown) I think I figured it out. Here is a patch along these lines. I named the three counters "sessions_client_eof", "sessions_fatal" and "sessions_killed", but I am not wedded to these bike shed colors. Yours, Laurenz Albe
Commits
-
Bump PGSTAT_FILE_FORMAT_ID
- b2f87b46690a 14.0 landed
-
Add pg_stat_database counters for sessions and session time
- 960869da0803 14.0 landed
-
Fix oversight in my patch of yesterday: forgot to ensure that stats would
- 641912b4d17f 8.3.0 cited