Re: Redundant/mis-use of _(x) gettext macro?
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Peter Smith <smithpb2250@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Peter Eisentraut <peter@eisentraut.org>
Date: 2026-06-11T20:21:16Z
Lists: pgsql-hackers
On 2026-Jun-11, Álvaro Herrera wrote: > In the end I decided to go with the flow and changed to use "first" > logic rather than "last". I also figured that we should change the > other two places you pointed out at the start of the thread to use the > same coding style. Since this is mostly cosmetic, I don't feel > compelled to back-patch it, and pushed only to master. > > Another place I noticed while looking this over is psql's > describeOneTableDetails(), per the attached patch. It's essentially > more of the same, but arguably different enough that I judged it > warranted posting before pushing. Crap, I just noticed that Peter Eisentraut had made himself committer of this CF entry. Apologies, I've had this marked as pending on my inbox for so long that it didn't occur to me to check the CF page. -- Álvaro Herrera 48°01'N 7°57'E — https://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 →
-
Fix translatable string construction in psql
- 5459223edb1d 19 (unreleased) landed
-
Fix translatable string construction
- 3692a622d3fd 19 (unreleased) landed