Message-ID: <gh-pgjdbc-pgjdbc-3939-c3944375183@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 23 Feb 2026 12:05:41 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3939: Add RequireServerVersion annotation for tests
In-Reply-To: <gh-pgjdbc-pgjdbc-3939@github.com>
References: <gh-pgjdbc-pgjdbc-3939@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 3944375183
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3939
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3939#issuecomment-3944375183
Content-Type: text/plain; charset=utf-8

For reference, JUnit has both `@DisabledForJreRange` and `@EnabledForJreRange` because their `min` and `max` are always `inclusive`, so they need two annotations to distinguish between `less than` and `less or equal than`.

However, if we allow `minInclusive / maxInclusive` customization (or the current lt/lte/gt/gte), we don't really need a counterpart `@Disabled...` annotation.