Re: Get rid of translation strings that only contain punctuation

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Get rid of translation strings that only contain punctuation
Date: 2026-04-22 12:13:01
Message-ID: CAA4eK1+36hfrHqTut-M0YRgy7LiEEkuwWZ97M0bc7FKg=2Eu9g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 22, 2026 at 6:21 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> We previously discussed the append_tuple_value_detail case [1], and
> I opined that the right fix was to change things so that what that
> function produces is a string that doesn't need translation because
> it matches SQL syntax for a row constructor. It doesn't look like
> that's happened yet.
>

I'll look into your suggestions.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2026-04-22 12:32:23 Re: Two issues leading to discrepancies in FSM data on the standby server
Previous Message shveta malik 2026-04-22 12:05:17 Re: Parallel Apply