From: "Pavlo Golub" <pavlo.golub@cybertec.at>
To: "Sami Imseih" <samimseih@gmail.com>
Subject: Re[2]: [PATCH] Add last_executed timestamp to pg_stat_statements
Cc: pgsql-hackers@lists.postgresql.org
Date: Thu, 11 Dec 2025 11:31:39 +0000
Message-Id: <em5be966c3-9086-4f3f-b516-97444b854fdf@10e48d49.com>
In-Reply-To: 
 <CAA5RZ0uyvnNuHRj=73jZhocnLxE07oM-AeSLS=FUuuZ_hy7fKA@mail.gmail.com>
References: 
 <CAK7ymc+FxoVswo1ok_xDW-xPG-ZEZ8SAqCUkJ7WF04=0aQDvVQ@mail.gmail.com>
 <CAA5RZ0uyvnNuHRj=73jZhocnLxE07oM-AeSLS=FUuuZ_hy7fKA@mail.gmail.com>
Reply-To: "Pavlo Golub" <pavlo.golub@cybertec.at>
User-Agent: eM_Client/10.3.2619.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/em5be966c3-9086-4f3f-b516-97444b854fdf%4010e48d49.com>
Precedence: bulk

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=20
between snapshots.
Data for every statement is changes after each execution.

But stats_since is inserted only once when the new statement execution=20
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+kD=
eTktAtC-KY9fQ9Z6BJdDUirQ@mail.gmail.com
>[1] https://www.postgresql.org/message-id/03f82e6f-66a3-4c4d-935c-ea4d9387=
1dc1%40gmail.com
>
>--
>Sami Imseih
>Amazon Web Services (AWS)