Fix pg_stat_statements for MERGE
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 27 Sep 2022 08:44:42 +0000 (10:44 +0200)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 27 Sep 2022 08:44:42 +0000 (10:44 +0200)
commit249b0409b181311bb1c375311e43eb767b5c3bdd
tree4fe99b3693dde97b23c63b2505e2a4ae74ab6297
parentbed0927aeb0c61bd8649b56e5b84a6d551d5f416
Fix pg_stat_statements for MERGE

We weren't jumbling the merge action list, so wildly different commands
would be considered to use the same query ID.  Add that, mention it in
the docs, and some test lines.

Backpatch to 15.

Author: Tatsu <bt22nakamorit@oss.nttdata.com>
Reviewed-by: Julien Rouhaud <rjuju123@gmail.com>
Discussion: http://postgr.es/m/d87e391694db75a038abc3b2597828e8@oss.nttdata.com
contrib/pg_stat_statements/expected/pg_stat_statements.out
contrib/pg_stat_statements/sql/pg_stat_statements.sql
doc/src/sgml/pgstatstatements.sgml
src/backend/nodes/nodeFuncs.c
src/backend/utils/misc/queryjumble.c