Message-ID: <gh-pgjdbc-pgjdbc-3365-c2792099430@github.com>
From: "MrEasy (@MrEasy)" <noreply+MrEasy@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 10 Apr 2025 09:15:42 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
In-Reply-To: <gh-pgjdbc-pgjdbc-3365@github.com>
References: <gh-pgjdbc-pgjdbc-3365@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: MrEasy
X-GitHub-Comment-Id: 2792099430
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3365
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3365#issuecomment-2792099430
Content-Type: text/plain; charset=utf-8

> Would anyone be unhappy with [@rbrw](https://github.com/rbrw) 's patch applied? If this doesn't get fixed upstream, I might put the patch into the Debian package to get the PuppetDB issue resolved.

Me (as humble reporter) would be fine with anything fixing it - see my test-case that is attached to https://github.com/pgjdbc/pgjdbc/pull/3369