Message-ID: <gh-pgjdbc-pgjdbc-3930-c3890486779@github.com>
From: "AFulgens (@AFulgens)" <noreply+AFulgens@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 12 Feb 2026 11:53:02 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3930: Revert semantic calendar changes introduced with #3837
In-Reply-To: <gh-pgjdbc-pgjdbc-3930@github.com>
References: <gh-pgjdbc-pgjdbc-3930@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: AFulgens
X-GitHub-Comment-Id: 3890486779
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3930
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3930#issuecomment-3890486779
Content-Type: text/plain; charset=utf-8

@davecramer I thought that's what you meant with "we will enteratain this with a configuration switch" (sorry, I used "feature flag", working with microservices most of the time 😅 ). As long as the default behaviour is rolled back to what it was, all is fine.

@m-van-tilburg 
> Luckily there was and is a workaround to get the correct values by using the java.time based JDBC methods. Lets close the discussion now.

That's sadly not a feasible workaround for a code-base of over 2M lines with 15 years of commit history.

But yes, let's close the discussion and leave the maintainers some breathing room 😀