pgsql: Track more precisely query locations for nested statements

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Track more precisely query locations for nested statements
Date: 2024-10-24 00:31:05
Message-ID: E1t3lkn-0029Yd-UO@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Track more precisely query locations for nested statements

Previously, a Query generated through the transform phase would have
unset stmt_location, tracking the starting point of a query string.

Extensions relying on the statement location to extract its relevant
parts in the source text string would fallback to use the whole
statement instead, leading to confusing results like in
pg_stat_statements for queries relying on nested queries, like:
- EXPLAIN, with top-level and nested query using the same query string,
and a query ID coming from the nested query when the non-top-level
entry.
- Multi-statements, with only partial portions of queries being
normalized.
- COPY TO with a query, SELECT or DMLs.

This patch improves things by keeping track of the statement locations
and propagate it to Query during transform, allowing PGSS to only show
the relevant part of the query for nested query. This leads to less
bloat in entries for non-top-level entries, as queries can now be
grouped within the same (toplevel, queryid) duos in pg_stat_statements.
The result gives a stricter one-one mapping between query IDs and its
query strings.

The regression tests introduced in 45e0ba30fc40 produce differences
reflecting the new logic.

Author: Anthonin Bonnefoy
Reviewed-by: Michael Paquier, Jian He
Discussion: https://postgr.es/m/CAO6_XqqM6S9bQ2qd=75W+yKATwoazxSNhv5sjW06fjGAtHbTUA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/499edb09741b8fad2de038361fb342aae6e6007f

Modified Files
--------------
.../pg_stat_statements/expected/level_tracking.out | 165 ++++++++++-----------
contrib/pg_stat_statements/expected/planning.out | 10 +-
contrib/pg_stat_statements/expected/select.out | 2 +-
contrib/pg_stat_statements/expected/utility.out | 2 +-
contrib/pg_stat_statements/sql/planning.sql | 4 +-
src/backend/parser/analyze.c | 95 +++++++++++-
src/backend/parser/gram.y | 80 +++++++++-
src/include/nodes/parsenodes.h | 10 ++
src/include/parser/parse_node.h | 16 ++
9 files changed, 280 insertions(+), 104 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2024-10-24 11:36:08 pgsql: Avoid looping over all type cache entries in TypeCacheRelCallbac
Previous Message Jeff Davis 2024-10-23 23:19:21 pgsql: Improve pg_set_attribute_stats() error message.