Re: Broken PQtrace CopyData display

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Ran Benita <ran(at)unusedvar(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Broken PQtrace CopyData display
Date: 2025-09-06 08:42:25
Message-ID: 202509060842.ypddmnwlfyaz@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2025-Sep-03, Michael Paquier wrote:

> On Sun, Aug 31, 2025 at 01:53:50PM +0900, Michael Paquier wrote:
> > Yeah. Not a lot of people use the libpq tracing, but it would be
> > better to show non-printable data in a consistent way.
>
> Done this one with db9405493b48.

Thanks!

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"La persona que no quería pecar / estaba obligada a sentarse
en duras y empinadas sillas / desprovistas, por cierto
de blandos atenuantes" (Patricio Vogel)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-09-06 20:31:53 Re: 回复:BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
Previous Message Greg Sabino Mullane 2025-09-06 00:41:43 Re: BUG #19043: jdbc connection url is not case insensitive