Commit9453798

committed

Remove obsolete comment in pg_stat_statements.

Commit76db9cb removed the use of multiple nesting counters,but missed one comment describing that arrangement.Back-patch to v17 where76db9cb came in, just to avoid confusion.Julien RouhaudDiscussion:https://postgr.es/m/gfcwh3zjxc2vygltapgo7g6yacdor5s4ynr234b6v2ohhuvt7m@gr42joxalenw

1 parent76f2a0e commit9453798Copy full SHA for 9453798

File tree

-7

lines changed

-7

lines changed

Lines changed: 0 additions & 7 deletions

Original file line number	Diff line number	Diff line change
`@@ -886,13 +886,6 @@ pgss_planner(Query *parse,`
`886`	`886`	`* We can't process the query if no query_string is provided, as`
`887`	`887`	`* pgss_store needs it. We also ignore query without queryid, as it would`
`888`	`888`	`* be treated as a utility statement, which may not be the case.`
`889`		`- *`
`890`		`- * Note that planner_hook can be called from the planner itself, so we`
`891`		`- * have a specific nesting level for the planner. However, utility`
`892`		`- * commands containing optimizable statements can also call the planner,`
`893`		`- * same for regular DML (for instance for underlying foreign key queries).`
`894`		`- * So testing the planner nesting level only is not enough to detect real`
`895`		`- * top level planner call.`
`896`	`889`	`*/`
`897`	`890`	`if (pgss_enabled(nesting_level)`
`898`	`891`	`&&pgss_track_planning&&query_string`

Comments

(0)