Re: Broken PQtrace CopyData display

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>

To: Michael Paquier <michael@paquier.xyz>

Cc: Ran Benita <ran@unusedvar.com>, pgsql-bugs@lists.postgresql.org

Date: 2025-09-06T08:42:25Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

libpq: Fix PQtrace() format for non-printable characters
- 0cc540f0d03f 14.20 landed
- 0b274c4759a9 15.15 landed
- 701a0bd56aa4 16.11 landed
- 0fedb3a27d24 17.7 landed
- ae53537e218a 18.0 landed
- db9405493b48 19 (unreleased) landed

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)