Re: [PATCH v5] pg_stat_statements: Add last_execution_start column - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: [PATCH v5] pg_stat_statements: Add last_execution_start column
Date
Msg-id CAN4CZFNbJtY_k6KeJHCgaYN=3XYghOHNjdrUuaA6h2jxux-V+A@mail.gmail.com
Whole thread
In response to [PATCH v5] pg_stat_statements: Add last_execution_start column  ("Pavlo Golub" <pavlo.golub@cybertec.at>)
Responses Re: [PATCH v5] pg_stat_statements: Add last_execution_start column
List 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%';



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why our Valgrind reports suck
Next
From: Sami Imseih
Date:
Subject: Re: [PATCH v5] pg_stat_statements: Add last_execution_start column