pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #4016: feat: harden protocol reader against desynced streams (#4015)
Date: Tue, 26 May 2026 06:28:28 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
> There's no point in having enablement modes
The `pgjdbc.protocolViolationBehaviour` property does not relax protocol invariants. Checks that prove the stream is desynced remain fatal in every mode. The property only affects defensive hardening bounds where the PostgreSQL protocol does not define a strict maximum, such as the `1 MiB` caps for `NotificationResponse` and `ParameterStatus`. Those caps are intended to catch desyncs early, but because they are pgjdbc-chosen compatibility limits rather than protocol limits, the default is `warn`.
view thread (21+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #4016: feat: harden protocol reader against desynced streams (#4015)
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox