From: Michael Paquier <michael@paquier.xyz>
To: Ran Benita <ran@unusedvar.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Broken PQtrace CopyData display
Date: Wed, 3 Sep 2025 12:58:45 +0900
Message-ID: <aLe89ZdYSZZit_u0@paquier.xyz> (raw)
In-Reply-To: <aLPVXkOipoBSWSb1@paquier.xyz>
References: <a3383211-4539-459b-9d51-95c736ef08e0@app.fastmail.com>
<aLPVXkOipoBSWSb1@paquier.xyz>
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
Attachments:
[application/pgp-signature] signature.asc (832B, ../aLe89ZdYSZZit_u0@paquier.xyz/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, ran@unusedvar.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Broken PQtrace CopyData display
In-Reply-To: <aLe89ZdYSZZit_u0@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox