Re: Another incorrect comment for pg_stat_statements

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Japin Li <japinli(at)hotmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Another incorrect comment for pg_stat_statements
Date: 2023-06-28 07:09:55
Message-ID: CAMbWs49gd77hXoD=cG7KfUJd56Fx3b8JwQxt1wShbAXYg2yjOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 28, 2023 at 3:04 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> 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.

+1. To nitpick, how about we remove the blank line just before removing
the key for top level entry?

- /* Also remove entries for top level statements */
+ /* Also remove entries if exist for top level statements */
key.toplevel = true;
-
- /* Remove the key if exists */
entry = (pgssEntry *) hash_search(pgss_hash, &key, HASH_REMOVE, NULL);

Thanks
Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2023-06-28 07:29:39 removing limitations from bitmap index scan
Previous Message Michael Paquier 2023-06-28 07:04:48 Re: Another incorrect comment for pg_stat_statements