Re: Broken PQtrace CopyData display

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Ran Benita <ran@unusedvar.com>

Cc: pgsql-bugs@lists.postgresql.org

Date: 2025-09-03T03:58:45Z

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 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.
--
Michael