Re: [PATCH] Add last_executed timestamp to pg_stat_statements

From: Pavlo Golub <pavlo(dot)golub(at)cybertec(dot)at>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Christoph Berg <myon(at)debian(dot)org>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Add last_executed timestamp to pg_stat_statements
Date: 2026-02-17 08:30:26
Message-ID: CAK7ymc+Kr7i6p_6Hw_2hEg3xVRH8FYnnrEp0PHg+jeMvqH7mLg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

> I am not sure if this benchmark is enough to build confidence in this approach.
> Workloads with nested queries and tack. 'all' are now paying an even heavier
> cost.

I would love to see and test sql that will reveal the bigger overhead.
Do you have something specific on your mind? I'd love to share
results, we can use them later considering further updates to pgss.

>
> Also, quickly looking at v4, you probably want to call GetCurrentTimestamp()
> when kind == PGSS_EXEC only.

Fair enough! Thanks for noticing!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2026-02-17 08:38:32 Re: Don't keep closed WAL segment in page cache after replay
Previous Message Peter Eisentraut 2026-02-17 08:30:02 Re: [PATCH] Provide support for trailing commas