Thread
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix some issues with tracking nesting level in pg_stat_statements.
- 76db9cb6368e 17.0 cited
-
[PATCH v1] Remove obsolete comment in pg_stat_statements
Julien Rouhaud <julien.rouhaud@free.fr> — 2024-09-14T04:18:19Z
Commit 76db9cb6368 removed the use of multiple nesting counters but missed an associated comment. --- contrib/pg_stat_statements/pg_stat_statements.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/contrib/pg_stat_statements/pg_stat_statements.c b/contrib/pg_stat_statements/pg_stat_statements.c index 362d222f63..3c72e437f7 100644 --- a/contrib/pg_stat_statements/pg_stat_statements.c +++ b/contrib/pg_stat_statements/pg_stat_statements.c @@ -886,13 +886,6 @@ pgss_planner(Query *parse, * We can't process the query if no query_string is provided, as * pgss_store needs it. We also ignore query without queryid, as it would * be treated as a utility statement, which may not be the case. - * - * Note that planner_hook can be called from the planner itself, so we - * have a specific nesting level for the planner. However, utility - * commands containing optimizable statements can also call the planner, - * same for regular DML (for instance for underlying foreign key queries). - * So testing the planner nesting level only is not enough to detect real - * top level planner call. */ if (pgss_enabled(nesting_level) && pgss_track_planning && query_string -- 2.46.0 --apb45rsms6uvtvzn--