Re: Typo in comment for pgstat_database_flush_cb()

Gurjeet Singh <gurjeet@singh.im>

From: "Gurjeet Singh" <gurjeet@singh.im>
To: "Heikki Linnakangas" <hlinnaka@iki.fi>, "Etsuro Fujita" <etsuro.fujita@gmail.com>, "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>
Date: 2025-03-30T17:54:08Z
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




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix typos in comments.