Re: lwlocknames.h beautification attempt

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Álvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Gurjeet Singh <gurjeet@singh.im>, Postgres Hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-17T13:10:06Z
Lists: pgsql-hackers
On Mon, Mar 17, 2025 at 2:43 AM Álvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Tom didn't say he didn't like this change.  He said he didn't like a
> different change, which is not the one I committed.

Sorry, I should have read the emails more carefully. I missed the fact
that there were two different proposals. It was the idea of
right-aligning things that I was unhappy about.

So, no objection to what you actually committed... except that I don't
think that using % specifiers in SOME places in a format string is
better than using them in ALL the places. It's not broken because
$lockidx can't contain a % sign, but in general I think when we switch
from print to printf it's better for us to have the format string be a
constant so that it's clear that we can't accidentally get an extra %
escape in there depending on the values of variables being
interpolated.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Make lwlocknames.h generated file less ugly