pg.ddx.io  GitHub: pgjdbc/pgjdbc (issues + PRs as email threads)  
help / color / mirror / Atom feed
From: vlsi (@vlsi) <noreply+vlsi@github.com>
To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>
Subject: Re: [pgjdbc/pgjdbc] PR #4332: fix: limit FINEST Bind, Parse and SimpleQuery log messages to maxLogMessageLength to avoid OOM
Date: Wed, 14 Oct 2026 06:22:27 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4332-rc4267444424@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4332@github.com>
References: <gh-pgjdbc-pgjdbc-4332@github.com>

(on pgjdbc/src/main/java/org/postgresql/core/v3/SimpleParameterList.java)

No test binds `setBytea(int, InputStream, int)` or `setText(int, InputStream)`, or leaves a parameter unset. For both streams this returns `2 * n + 11`, 211 for 100 bytes, while the trace shows `?` and `('<stream of 100 bytes>')`, so the Javadoc's "lower bound on rendered log size" and "raw bytes for binary payloads" no longer describe the code. The same `bytea` stream is logged as `$1=<?>` at the default limit and as `$1=<<100 bytes>>` at 120. Please make the Javadoc match the code, log a `bytea` stream the same way at every limit, and add a `BindLogTest` case for each of these value kinds with the exact expected line.

view thread (58+ messages)  latest in thread

Message-ID: <gh-pgjdbc-pgjdbc-4332-rc4267444424@github.com>
Permalink:  ../gh-pgjdbc-pgjdbc-4332-rc4267444424@github.com/

 · 


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