Re: [PATCH v5] pg_stat_statements: Add last_execution_start column
Zsolt Parragi <zsolt.parragi@percona.com>
From: Zsolt Parragi <zsolt.parragi@percona.com>
To: pgsql-hackers@lists.postgresql.org
Date: 2026-06-10T21:21:10Z
Lists: pgsql-hackers
I have one more question: should statements that failed have an execution start set? CREATE TABLE t(d int); INSERT INTO t VALUES (0); SELECT pg_stat_statements_reset(); SELECT now() AS ref_ts \gset SELECT 1/d FROM t; SELECT calls, plans, query FROM pg_stat_statements WHERE last_execution_start >= :'ref_ts' AND query LIKE '%/d FROM t%';
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_stat_statements: Set PlannedStmt to NULL after nested utility execution
- 66366217822e 19 (unreleased) cited