Re: Typo in comment for pgstat_database_flush_cb()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Gurjeet Singh <gurjeet(at)singh(dot)im>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Typo in comment for pgstat_database_flush_cb()
Date: 2025-04-06 21:44:31
Message-ID: Z_L1vxEm-mEFkyuf@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 06, 2025 at 01:31:50PM +0200, Etsuro Fujita wrote:
> +1 for both suggestions. So I modified the comment as such in each
> file with such a flush_cb function. I will push the patch.

Thanks for the fix. Could you also backpatch that down to v15? It
would be good to keep this level of comment documentation consistent
across all branches.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-04-06 21:49:02 Re: [PATCH] clarify palloc comment on quote_literal_cstr
Previous Message Andrew Dunstan 2025-04-06 21:10:51 Re: getting "shell command argument contains a newline or carriage return:" error with pg_dumpall when db name have new line in double quote