Message-ID: <gh-pgjdbc-pgjdbc-4016-c4372333428@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 04 May 2026 15:32:22 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #4016: feat: harden protocol reader against desynced streams (#4015)
In-Reply-To: <gh-pgjdbc-pgjdbc-4016@github.com>
References: <gh-pgjdbc-pgjdbc-4016@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 4372333428
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2026-05-26T11:55:00Z
X-GitHub-Issue: 4016
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4016#issuecomment-4372333428
Content-Type: text/plain; charset=utf-8

~I think this requires a minor version bump.~
UPD: I think the change is safe to merge in patch version as it should not harm benign workflows.

The tests pass, and I am happy with the added hardenings.

Comments are welcome.

@duwenice, it would be great if you could run the hardened build in your environment to check it it detects violations or introduces false positives.