Message-ID: <gh-pgjdbc-pgjdbc-2311-c2668688040@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 19 Feb 2025 13:39:57 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2311: Why is client time zone not configurable?
In-Reply-To: <gh-pgjdbc-pgjdbc-2311@github.com>
References: <gh-pgjdbc-pgjdbc-2311@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2668688040
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2311
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2311#issuecomment-2668688040
Content-Type: text/plain; charset=utf-8

> What value of user.timezone is necessary for pgjdbc to work in America/Ciudad_Juarez? And every other places in the Pacific.

It would help if you reviewed the server documentation on how timestamps with time zone are handled. The server does not store the timezone. When storing the timestamp it is converted to UTC based on the setting of the timezone. When it is retrieved it is converted back to the setting of the timezone. This is why we set it to the JVM timezone so that all of the time conversions "just work" 

In your case since you are managing your timestamps yourself not setting it or setting it to something different than the JVM works fine. However it won't work fine for everyone else. 

As @vlsi  mentioned create a PR. (You mentioned you have already hacked the driver) and let's see if it passes all of the tests. 

I get that you are frustrated, but as @vlsi mentioned please try working with us. We have a much bigger audience than just you. There are good reasons why just changing something to fix your problem may not be the correct thing to do.