Hi
Hi,
Thanks for raising this. I did not look at the patch, but I have some high
level comments.
I would like to propose adding a last_executed timestamptz column to
pg_stat_statements. This column records when each tracked statement
was most recently executed.
I do think there is value in adding a last_executed timestamp.
Thanks for your support!
Can pg_stat_statements.stats_since help here?
for example "where stats_since > last_poll_timestamp" ?
Actually no, monitoring tools fetch snapshots to find the difference
between snapshots.
Data for every statement is changes after each execution.
But stats_since is inserted only once when the new statement execution
appears and is never updated during next executions.
The client does have to track the last_poll_timestamp in that
case.
[0]
https://www.postgresql.org/message-id/flat/caa5rz0s9sdou+z6veojchwk+kdetktatc-ky9fq9z6bjddu...@mail.gmail.com
[1]
https://www.postgresql.org/message-id/03f82e6f-66a3-4c4d-935c-ea4d93871dc1%40gmail.com
--
Sami Imseih
Amazon Web Services (AWS)
