Fix pg_stat_statements for MERGE
Alvaro Herrera <alvherre@alvh.no-ip.org>
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: https://postgr.es/m/d87e391694db75a038abc3b2597828e8@oss.nttdata.com
Files
| Path | Change | +/− |
|---|---|---|
| contrib/pg_stat_statements/expected/pg_stat_statements.out | modified | +40 −1 |
| contrib/pg_stat_statements/sql/pg_stat_statements.sql | modified | +22 −0 |
| doc/src/sgml/pgstatstatements.sgml | modified | +2 −2 |
| src/backend/nodes/nodeFuncs.c | modified | +2 −2 |
| src/backend/utils/misc/queryjumble.c | modified | +11 −0 |
Documentation touched
Discussion
- Differentiate MERGE queries with different structures 5 messages · 2022-09-26 → 2022-09-27