Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit234ba62

Browse files
committed
pg_stat_statements: Remove obsolete comment
Since4f0b096, pgss_store() does nothing if compute_query_id is disabledor if no other module computed a query identifier, but the top commentof this function did not reflect that. This behavior is alreadydocumented in its own code path, and this just removes the inconsistentcomment.Author: Kyotaro HoriguchiReviewed-by: Julien RouhaudDiscussion:https://postgr.es/m/20211122.153823.1325120762360533122.horikyota.ntt@gmail.comBackpatch-through: 14
1 parent69872d0 commit234ba62

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

‎contrib/pg_stat_statements/pg_stat_statements.c‎

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1191,10 +1191,6 @@ pgss_ProcessUtility(PlannedStmt *pstmt, const char *queryString,
11911191
/*
11921192
* Store some statistics for a statement.
11931193
*
1194-
* If queryId is 0 then this is a utility statement for which we couldn't
1195-
* compute a queryId during parse analysis, and we should compute a suitable
1196-
* queryId internally.
1197-
*
11981194
* If jstate is not NULL then we're trying to create an entry for which
11991195
* we have no statistics as yet; we just want to record the normalized
12001196
* query string. total_time, rows, bufusage and walusage are ignored in this

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp