Message-ID: <gh-pgjdbc-pgjdbc-3757-c3176498882@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 11 Aug 2025 19:14:15 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3757: PreparedStatement.toString() fails for bytea parameters with at least 42.7.7
In-Reply-To: <gh-pgjdbc-pgjdbc-3757@github.com>
References: <gh-pgjdbc-pgjdbc-3757@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 3176498882
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3757
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3757#issuecomment-3176498882
Content-Type: text/plain; charset=utf-8

> Are "bytea" PGobjects with "\xHEX" syntax something pgjdbc intended to support, or was that support just incidental before? If the latter, and it's not documented / commonly used (perhaps it's just PuppetDB?), then I assume another option might be to avoid the additional complexity by just rejecting them in a way that doesn't crash toString.

No, \xHEX are not special see https://www.postgresql.org/docs/current/datatype-binary.html