From: Julien Rouhaud <rjuju123@gmail.com>
To: Jerry Brenner <jbrenner@guidewire.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Include a timestamp in future versions of pg_stat_statements when when a query entered the cache?
Date: Wed, 6 Dec 2023 07:45:07 +0100
Message-ID: <ZXAYc2UV5vdUTADo@jrouhaud> (raw)
In-Reply-To: <CACoKFYQ6DBsKbVLSA9BOGsWsP3U17Le0Cu_QrwGOEk2kPOoyMw@mail.gmail.com>
References: <CACoKFYQ6DBsKbVLSA9BOGsWsP3U17Le0Cu_QrwGOEk2kPOoyMw@mail.gmail.com>
Hi,
On Tue, Dec 05, 2023 at 06:28:54AM -0800, Jerry Brenner wrote:
> It would be helpful if a timestamp column was added to pg_stat_statements
> to denote when a query entered the view. This would make it easier to tell
> how frequently a query is being executed (100,000 times since a specific
> timestamp vs 100,000 times since the execution stats were last reset.)
This was actually done a few weeks ago, and will be available with pg 17. You
can see the 2 new timestamp counters (one for the whole record, one for the
minmax counters only) documentation at
https://www.postgresql.org/docs/devel/pgstatstatements.html
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: pgsql-performance@postgresql.org
Cc: rjuju123@gmail.com, jbrenner@guidewire.com, pgsql-performance@lists.postgresql.org
Subject: Re: Include a timestamp in future versions of pg_stat_statements when when a query entered the cache?
In-Reply-To: <ZXAYc2UV5vdUTADo@jrouhaud>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox