Re: pgsql: Make escaping functions retain trailing bytes of an invalid char

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Make escaping functions retain trailing bytes of an invalid char
Date: 2025-05-01 21:15:40
Message-ID: 1658526.1746134140@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 15.02.25 22:20, Tom Lane wrote:
>> Make escaping functions retain trailing bytes of an invalid character.

> I think the backpatch of this to PG15 and older has erroneously dropped
> newlines at the end of some error messages.

Oh! You're right, though I'd phrase it differently: I should have
*added* newlines when back-patching into those branches. Will fix.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robins Tharakan 2025-05-01 21:17:27 Re: pgsql: doc: Warn that ts_headline() output is not HTML-safe.
Previous Message Peter Eisentraut 2025-05-01 21:04:27 Re: pgsql: Make escaping functions retain trailing bytes of an invalid char