Re: Redundant/mis-use of _(x) gettext macro?

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Redundant/mis-use of _(x) gettext macro?
Date: 2026-06-11 20:21:16
Message-ID: aisX7lLTLDJY4I4W@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Taylor 2026-06-11 20:40:19 Re: Remove redundant DISTINCT when GROUP BY already guarantees uniqueness
Previous Message Masahiko Sawada 2026-06-11 19:20:17 Re: uuidv7 improperly accepts dates before 1970-01-01