| From: | Pavlo Golub <pavlo(dot)golub(at)cybertec(dot)at> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | [PATCH v4] pg_stat_statements: Add last_execution_start column |
| Date: | 2026-05-13 14:38:20 |
| Message-ID: | CAK7ymcKezuTN43OQp0m5rcgqi9uZEBAknTyNiDmktRmxnFBq1g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Rebased on current master (a3e6beba60e).
The only conflict was with commit 66366217822 (pg_stat_statements: Set
PlannedStmt to NULL after nested utility execution), which introduced a
local copy of pstmt->planOrigin and then nulled pstmt. The patch context
line was updated to reference saved_planOrigin instead. No functional
changes from v3.
All pg_stat_statements regression tests pass (16/16).
v4 patch attached.
Best regards,
Pavlo Golub
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-pg_stat_statements-Add-last_execution_start-colum.patch | application/octet-stream | 23.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-05-13 14:57:29 | Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION |
| Previous Message | Nathan Bossart | 2026-05-13 14:23:26 | Re: Experimental patch for terminating VACUUM freeze blockers |