From 62c1bfd2f4961a513195e2cdae33c5bc8204061e Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Mon, 20 May 2024 15:16:54 +0900 Subject: [PATCH] doc: Fix incorrect reference to query ID generation The query ID is automatically computed by PostgreSQL if the GUC compute_query_id is set to "on" or "auto". pg_hint_plan informs the backend to compute the query ID when pg_hint_plan.enable_hint_table is enabled by calling EnableQueryId() for the "auto" case. The documentation incorrectly mentioned that query IDs are computed by pg_stat_statements, so let's fix the description to match with the real behavior. Query IDs are computed by PostgreSQL itself without pg_stat_statement's help since v14, so backpatch down to this version. Backpatch-through: 14 --- docs/functional_limitations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/functional_limitations.md b/docs/functional_limitations.md index de016065..1c300c19 100644 --- a/docs/functional_limitations.md +++ b/docs/functional_limitations.md @@ -23,8 +23,8 @@ ECPG removes comments in queries written as embedded SQLs so hints cannot be passed to it. The only exception `EXECUTE`, that passes the query string to the server as-is. The hint table can be used in the case. -## `pg_stat_statements` +## Query Identifiers -`pg_stat_statements` generates a query ID, ignoring comments. Hence, -queries with different hints, still written the same way, may compute the -same query ID. +When `compute_query_id` is enabled, PostgreSQL generates a query ID, +ignoring comments. Hence, queries with different hints, still written +the same way, may compute the same query ID.