Message-ID: <gh-pgjdbc-pgjdbc-3944-c3944390093@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 23 Feb 2026 12:09:00 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone
In-Reply-To: <gh-pgjdbc-pgjdbc-3944@github.com>
References: <gh-pgjdbc-pgjdbc-3944@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 3944390093
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3944
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3944#issuecomment-3944390093
Content-Type: text/plain; charset=utf-8

Well, `java.sql` types do not have explicit timezone, so we have to convert the value as if it was in "the client's default timezone".
With OffsetDateTime we somehow decided to force UTC, and it causes inconsistency like in #1324.
I think we can use connection timezone when decoding OffsetDateTime, and we can convert UTC binary value into the client's time zone. However, if we ever do so, we should better discuss it in #1324.

This PR just adds extra clarification on the current behavior.