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 02:52:58 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4332-rc4266276837@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/BindLog.java)
A text value longer than the room left is logged as `...(~20000 chars)`, with none of its content, so the trace no longer shows what the statement ran on. For JSON or XML, a prefix is what makes the trace useful. For a `String` value, escape only its first `remaining` characters, cut the result to the room left without splitting a surrogate pair or a doubled quote, and end it with `...`. Escaping at most doubles the prefix, so the full literal is never built, and a cut value does not look complete.