pgsql: Bend parse location rules for the convenience of pg_stat_stateme - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Bend parse location rules for the convenience of pg_stat_stateme
Date
Msg-id E1SCbuA-0003M7-41@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Bend parse location rules for the convenience of pg_stat_statements.

Generally, the parse location assigned to a multiple-token construct is
the location of its leftmost token.  This commit breaks that rule for
the syntaxes TYPENAME 'LITERAL' and CAST(CONSTANT AS TYPENAME) --- the
resulting Const will have the location of the literal string, not the
typename or CAST keyword.  The cases where this matters are pretty thin on
the ground (no error messages in the regression tests change, for example),
and it's unlikely that any user would be confused anyway by an error cursor
pointing at the literal.  But still it's less than consistent.  The reason
for changing it is that contrib/pg_stat_statements wants to know the parse
location of the original literal, and it was agreed that this is the least
unpleasant way to preserve that information through parse analysis.

Peter Geoghegan

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5d3fcc4c2e137417ef470d604fee5e452b22f6a7

Modified Files
--------------
src/backend/parser/parse_coerce.c |   14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: New GUC, track_iotiming, to track I/O timings.
Next
From: Tom Lane
Date:
Subject: pgsql: Add some infrastructure for contrib/pg_stat_statements.