Teach pg_stat_statements not to ignore FOR UPDATE clauses
Performance of a SELECT FOR UPDATE may be quite distinct from the
non-UPDATE version of the query, so treat all of the FOR UPDATE clause
as being significant for distinguishing queries.
Andrew Gierth and Vik Fearing, reviewed by Sergei Kornilov, Thomas
Munro, Tom Lane
Discussion: https://postgr.es/m/87h8e4hfwv.fsf@news-spur.riddles.org.uk
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/6e74c64bcf61eab94091f6b17dfd0ab585b1a77e
Modified Files
--------------
.../expected/pg_stat_statements.out | 87 ++++++++++++++++++++++
contrib/pg_stat_statements/pg_stat_statements.c | 23 +++++-
.../pg_stat_statements/sql/pg_stat_statements.sql | 31 ++++++++
3 files changed, 140 insertions(+), 1 deletion(-)