Re: Another incorrect comment for pg_stat_statements
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Japin Li <japinli@hotmail.com>
Cc: Richard Guo <guofenglinux@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-06-28T07:04:48Z
Lists: pgsql-hackers
On Wed, Jun 28, 2023 at 12:15:47PM +0800, Japin Li wrote: > - /* Remove the key if it exists, starting with the top-level entry */ > + /* Remove the key if it exists, starting with the non-top-level entry */ > key.toplevel = false; > entry = (pgssEntry *) hash_search(pgss_hash, &key, HASH_REMOVE, NULL); > if (entry) /* found */ Nice catch. That's indeed wrong. Will fix. -- Michael
Commits
-
pg_stat_statements: Fix second comment related to entry resets
- 7e8349cbd7f7 14.9 landed
- e886124647ce 15.4 landed
- bc8e9a6a25e1 16.0 landed
-
pg_stat_statements: Fix incorrect comment with entry resets
- aa4b11e8be7d 14.9 landed
- a757e16b7e7c 15.4 landed
- dc73db67433c 16.0 landed
-
Track identical top vs nested queries independently in pg_stat_statements
- 6b4d23feef6e 14.0 cited