Re: Typo in comment for pgstat_database_flush_cb()

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: 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 11:39:35
Message-ID: f85b25f9-33da-4184-8c7f-0ed7ef087ac5@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

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

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-03-30 12:14:09 Re: Amcheck verification of GiST and GIN
Previous Message Heikki Linnakangas 2025-03-30 11:32:27 Re: Typo in comment for pgstat_database_flush_cb()