| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Tracking last scan time |
| Date: | 2022-08-31 18:11:11 |
| Message-ID: | Yw+kP+f49s/iLRR+@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 31, 2022 at 07:52:49PM +0200, Matthias van de Meent wrote:
> As for having a lower granularity and preventing the
> one-syscall-per-Relation issue, can't we reuse the query_start or
> state_change timestamps that appear in pg_stat_activity (potentially
Yeah, query start should be fine, but not transaction start time.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-08-31 18:11:54 | Re: [RFC] building postgres with meson - v12 |
| Previous Message | Jeremy Schneider | 2022-08-31 18:00:05 | Re: [PATCH] Query Jumbling for CALL and SET utility statements |