Message-ID: <gh-pgjdbc-pgjdbc-3837-c3396572481@github.com>
From: "ShenFeng312 (@ShenFeng312)" <noreply+ShenFeng312@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 13 Oct 2025 09:15:12 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3837: ResultSet.getTimestamp() returns incorrect point in time for historical dates
In-Reply-To: <gh-pgjdbc-pgjdbc-3837@github.com>
References: <gh-pgjdbc-pgjdbc-3837@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: ShenFeng312
X-GitHub-Comment-Id: 3396572481
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3837
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3837#issuecomment-3396572481
Content-Type: text/plain; charset=utf-8

his issue seems unrelated to JDBC. I observed that `TIMESTAMP_LOCAL_1000_AD` is already incorrect. It also seems to be caused by JDK behavior.