Re: BUG: pg_stat_statements query normalization issues with combined queries
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: robertmhaas@gmail.com,
PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2016-12-22T07:39:52Z
Lists: pgsql-hackers
Hello Kyotaro-san, > [...] Agreed that copying statement string would be too much. But the > new *Stmt node should somehow have also the end location of the > statement since the user of a parse tree cannot look into another one. Yes. I was thinking of adding a "length" field next to "location", where appropriate. >> So I'm rather still in favor of my initial proposal, that is extend >> the existing location information to statements, not only some tokens. > > I thought that it's too much to let all types of parse node have > location but grepping the gram.y with "makeNode" pursuaded me to > agree with you. Indeed... > After changing all *Stmt nodes, only several types of nodes seems > missing it. Yes. I'll try to put together a patch and submit it to the next CF. -- Fabien.
Commits
-
Teach contrib/pg_stat_statements to handle multi-statement commands better.
- 83f2061dd037 10.0 landed
-
Change representation of statement lists, and add statement location info.
- ab1f0c822571 10.0 landed
-
Revert my bad decision of about a year ago to make PortalDefineQuery
- 1591fcbec77f 8.4.0 cited