From: | Japin Li <japinli(at)hotmail(dot)com> |
---|---|
To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Another incorrect comment for pg_stat_statements |
Date: | 2023-06-28 13:26:02 |
Message-ID: | MEYP282MB16696B7FB5505879710AA2E4B624A@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 28 Jun 2023 at 16:27, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> On Wed, Jun 28, 2023 at 3:36 PM Michael Paquier <michael(at)paquier(dot)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.
>
+1. LGTM.
--
Regrads,
Japin Li.
From | Date | Subject | |
---|---|---|---|
Next Message | torikoshia | 2023-06-28 13:28:13 | Re: pg_rewind WAL segments deletion pitfall |
Previous Message | Terry Brennan | 2023-06-28 12:40:21 | Re: Request for new function in view update |