Re: [PATCH] clarify palloc comment on quote_literal_cstr - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: [PATCH] clarify palloc comment on quote_literal_cstr
Date
Msg-id CAExHW5sMbeyJgtq=Bk3f2AwmLBrTwoocxUD4Tq_4qUk_Hs04Xw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] clarify palloc comment on quote_literal_cstr  (Steve Chavez <steve@supabase.io>)
Responses Re: [PATCH] clarify palloc comment on quote_literal_cstr
List pgsql-hackers
On Tue, Apr 8, 2025 at 12:08 AM Steve Chavez <steve@supabase.io> wrote:
>
> I haven't found a similar style of comment on any other function call.
>
> I've attached a new patch using the style you suggest.
>
> That being said, I do find the first form much more readable, but I understand this is a debatable subject.

Thanks for addressing the comment.

In PG code, we start a multiline comment with just /* on the first
line and end with just */ on the last line. All the lines in-between
start with * . Please check other comments in the file.

I would write a., b. c. d. on separate lines.

--
Best Wishes,
Ashutosh Bapat



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [PoC] Reducing planning time when tables have many partitions
Next
From: Yugo NAGATA
Date:
Subject: Re: Extend ALTER DEFAULT PRIVILEGES for large objects