Message-ID: <gh-pgjdbc-pgjdbc-4016-c4543912095@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 26 May 2026 11:54:21 +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: 4543912095
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 4016
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4016#issuecomment-4543912095
Content-Type: text/plain; charset=utf-8

>  a minor version bump

That was a stale comment. Initially I thought the change could break benign workflows, however, now I think it is fine for patch change.
Every mandatory check implemented here comes from the protocol specification. The extra checks like `NotificationResponse ≤ 1 MiB` are "warning by default" as there might be PostgreSQL forks using 1MiB notifications for something useful.