Horton
Menu

Re: [PATCH] clarify palloc comment on quote_literal_cstr

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Steve Chavez <steve@supabase.io>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2025-04-08T06:30:24Z
Lists: pgsql-hackers 
On Tue, Apr 08, 2025 at 01:26:59AM -0400, Tom Lane wrote:
> +1.  When I saw the patch I was mainly afraid that pgindent would
> make a hash of it.

Yes.  I was actually surprised to see that it did not mess up with the
code generated.
--
Michael

Commits

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

  1. Clarify comment for worst-case allocation in quote_literal_cstr()