postgres/contrib/pg_stat_statements
Tom Lane 14e5680eee Improve parser's reporting of statement start locations.
Up to now, the parser's reporting of a statement's stmt_location
included any preceding whitespace or comments.  This isn't really
desirable but was done to avoid accounting honestly for nonterminals
that reduce to empty.  It causes problems for pg_stat_statements,
which partially compensates by manually stripping whitespace, but
is not bright enough to strip /*-style comments.  There will be
more problems with an upcoming patch to improve reporting of errors
in extension scripts, so it's time to do something about this.

The thing we have to do to make it work right is to adjust
YYLLOC_DEFAULT to scan the inputs of each production to find the
first one that has a valid location (i.e., did not reduce to
empty).  In theory this adds a little bit of per-reduction overhead,
but in practice it's negligible.  I checked by measuring the time
to run raw_parser() on the contents of information_schema.sql, and
there was basically no change.

Having done that, we can rely on any nonterminal that didn't reduce
to completely empty to have a correct starting location, and we don't
need the kluges the stmtmulti production formerly used.

This should have a side benefit of allowing parse error reports to
include an error position in some cases where they formerly failed to
do so, due to trying to report the position of an empty nonterminal.
I did not go looking for an example though.  The one previously known
case where that could happen (OptSchemaEltList) no longer needs the
kluge it had; but I rather doubt that that was the only case.

Discussion: https://postgr.es/m/ZvV1ClhnbJLCz7Sm@msg.df7cb.de
2024-10-22 11:26:05 -04:00
..
expected Improve parser's reporting of statement start locations. 2024-10-22 11:26:05 -04:00
sql Improve parser's reporting of statement start locations. 2024-10-22 11:26:05 -04:00
t Update copyright for 2024 2024-01-03 20:49:05 -05:00
.gitignore pg_stat_statements: Add .gitignore file for tests 2016-11-13 08:24:43 -05:00
Makefile pg_stat_statements: Add columns to track parallel worker activity 2024-10-09 08:30:45 +09:00
meson.build pg_stat_statements: Add columns to track parallel worker activity 2024-10-09 08:30:45 +09:00
pg_stat_statements--1.1--1.2.sql
pg_stat_statements--1.2--1.3.sql
pg_stat_statements--1.3--1.4.sql Update pg_stat_statements extension for parallel query. 2016-06-10 10:42:01 -04:00
pg_stat_statements--1.4--1.5.sql Default monitoring roles 2017-03-30 14:18:53 -04:00
pg_stat_statements--1.4.sql Update pg_stat_statements extension for parallel query. 2016-06-10 10:42:01 -04:00
pg_stat_statements--1.5--1.6.sql Revoke pg_stat_statements_reset() permissions 2018-09-25 09:55:44 +09:00
pg_stat_statements--1.6--1.7.sql Extend pg_stat_statements_reset to reset statistics specific to a 2019-01-11 08:50:09 +05:30
pg_stat_statements--1.7--1.8.sql Change the display of WAL usage statistics in Explain. 2020-05-05 08:00:53 +05:30
pg_stat_statements--1.8--1.9.sql Merge v1.10 of pg_stat_statements into v1.9 2021-04-08 15:15:17 +02:00
pg_stat_statements--1.9--1.10.sql Add JIT counters to pg_stat_statements 2022-04-08 13:52:16 +02:00
pg_stat_statements--1.10--1.11.sql Track statement entry timestamp in contrib/pg_stat_statements 2023-11-27 02:52:17 +02:00
pg_stat_statements--1.11--1.12.sql pg_stat_statements: Add columns to track parallel worker activity 2024-10-09 08:30:45 +09:00
pg_stat_statements--1.0--1.1.sql
pg_stat_statements.c pg_stat_statements: Add columns to track parallel worker activity 2024-10-09 08:30:45 +09:00
pg_stat_statements.conf Revert "pg_stat_statements: Add coverage for entry_dealloc()" 2023-12-31 15:30:57 +01:00
pg_stat_statements.control pg_stat_statements: Add columns to track parallel worker activity 2024-10-09 08:30:45 +09:00