Re: Another incorrect comment for pg_stat_statements - Mailing list pgsql-hackers

From Richard Guo
Subject Re: Another incorrect comment for pg_stat_statements
Date
Msg-id CAMbWs4-PkT_gdpzLoD_6aW2XaQCwzMN3JujXA6q4JXik=_dQzQ@mail.gmail.com
Whole thread Raw
In response to Re: Another incorrect comment for pg_stat_statements  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Another incorrect comment for pg_stat_statements
List pgsql-hackers

On Wed, Jun 28, 2023 at 3:36 PM Michael Paquier <michael@paquier.xyz> wrote:
On Wed, Jun 28, 2023 at 03:09:55PM +0800, Richard Guo wrote:
> +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);

Why not if it improves the overall situation.  Could you send a patch
with everything you have in mind?

Here is the patch.  I don't have too much in mind, so the patch just
removes the blank line and revises the comment a bit.

Thanks
Richard
Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Changing types of block and chunk sizes in memory contexts
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Support % wildcard in extension upgrade filenames