Re: Typo in comment for pgstat_database_flush_cb()

From: "Gurjeet Singh" <gurjeet(at)singh(dot)im>
To: "Heikki Linnakangas" <hlinnaka(at)iki(dot)fi>, "Etsuro Fujita" <etsuro(dot)fujita(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Typo in comment for pgstat_database_flush_cb()
Date: 2025-03-30 17:54:08
Message-ID: D8TSKFDCTU1C.IOW9D4G70B3C@singh.im
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun Mar 30, 2025 at 4:39 AM PDT, Heikki Linnakangas wrote:
> On 30/03/2025 14:32, Heikki Linnakangas wrote:
>> On 30/03/2025 13:28, Etsuro Fujita wrote:
>>> Another thing I noticed is $SUBJECT: I think “if lock could not
>>> immediately acquired” should be “if lock could not be immediately
>>> acquired”.  Attached is a patch for that.
>>
>> Yep. And there are more instances of the same typo in other such
>> flush_cb functions, if you search for "immediately acquired".

+1 for chainging other occurrences of this in other pgstat_*.c files.

> While we're at it, the comment feels a bit awkward to me anyway. Maybe
> rephrase it to "If nowait is true and the lock could not be immediately
> acquired, returns false without flushing the entry. Otherwise returns true."

This rephrasing does sounds better.

Best regards,
Gurjeet
http://Gurje.et

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2025-03-30 18:23:20 Re: AIO v2.5
Previous Message Andrew Dunstan 2025-03-30 16:50:51 Re: Non-text mode for pg_dumpall