postgres

History

Michael Paquier 7db9bfc1f7 Add missing query ID reporting in extended query protocol This commit adds query ID reports for two code paths when processing extended query protocol messages: - When receiving a bind message, setting it to the first Query retrieved from a cached cache. - When receiving an execute message, setting it to the first PlannedStmt stored in a portal. An advantage of this method is that this is able to cover all the types of portals handled in the extended query protocol, particularly these two when the report done in ExecutorStart() is not enough (neither is an addition in ExecutorRun(), actually, for the second point): - Multiple execute messages, with multiple ExecutorRun(). - Portal with execute/fetch messages, like a query with a RETURNING clause and a fetch size that stores the tuples in a first execute message going though ExecutorStart() and ExecuteRun(), followed by one or more execute messages doing only fetches from the tuplestore created in the first message. This corresponds to the case where execute_is_fetch is set, for example. Note that the query ID reporting done in ExecutorStart() is still necessary, as an EXECUTE requires it. Query ID reporting is optimistic and more calls to pgstat_report_query_id() don't matter as the first report takes priority except if the report is forced. The comment in ExecutorStart() is adjusted to reflect better the reality with the extended query protocol. The test added in pg_stat_statements is a courtesy of Robert Haas. This uses psql's \bind metacommand, hence this part is backpatched down to v16. Reported-by: Kaido Vaikla, Erik Wienhold Author: Sami Imseih Reviewed-by: Jian He, Andrei Lepikhov, Michael Paquier Discussion: https://postgr.es/m/CA+427g8DiW3aZ6pOpVgkPbqK97ouBdf18VLiHFesea2jUk3XoQ@mail.gmail.com Discussion: https://postgr.es/m/CA+TgmoZxtnf_jZ=VqBSyaU8hfUkkwoJCJ6ufy4LGpXaunKrjrg@mail.gmail.com Discussion: https://postgr.es/m/1391613709.939460.1684777418070@office.mailbox.org Backpatch-through: 14		12 months ago
..
expected	Add missing query ID reporting in extended query protocol	12 months ago
sql	Add missing query ID reporting in extended query protocol	12 months ago
t	Update copyright for 2024	2 years ago
.gitignore	pg_stat_statements: Add .gitignore file for tests	9 years ago
Makefile	Add missing query ID reporting in extended query protocol	12 months ago
meson.build	Add missing query ID reporting in extended query protocol	12 months ago
pg_stat_statements--1.0--1.1.sql	…
pg_stat_statements--1.1--1.2.sql	Keep pg_stat_statements' query texts in a file, not in shared memory.	12 years ago
pg_stat_statements--1.2--1.3.sql	Add stats for min, max, mean, stddev times to pg_stat_statements.	11 years ago
pg_stat_statements--1.3--1.4.sql	Update pg_stat_statements extension for parallel query.	9 years ago
pg_stat_statements--1.4--1.5.sql	Default monitoring roles	9 years ago
pg_stat_statements--1.4.sql	Update pg_stat_statements extension for parallel query.	9 years ago
pg_stat_statements--1.5--1.6.sql	Revoke pg_stat_statements_reset() permissions	7 years ago
pg_stat_statements--1.6--1.7.sql	Extend pg_stat_statements_reset to reset statistics specific to a	7 years ago
pg_stat_statements--1.7--1.8.sql	Change the display of WAL usage statistics in Explain.	5 years ago
pg_stat_statements--1.8--1.9.sql	Merge v1.10 of pg_stat_statements into v1.9	4 years ago
pg_stat_statements--1.9--1.10.sql	Add JIT counters to pg_stat_statements	3 years ago
pg_stat_statements--1.10--1.11.sql	Track statement entry timestamp in contrib/pg_stat_statements	2 years ago
pg_stat_statements.c	Remove obsolete comment in pg_stat_statements.	1 year ago
pg_stat_statements.conf	Revert "pg_stat_statements: Add coverage for entry_dealloc()"	2 years ago
pg_stat_statements.control	Add JIT deform_counter	2 years ago