Message-ID: <gh-pgjdbc-pgjdbc-2311-c2660690692@github.com>
From: "seregaizsbera (@seregaizsbera)" <noreply+seregaizsbera@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Sat, 15 Feb 2025 03:20:36 +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: seregaizsbera
X-GitHub-Comment-Id: 2660690692
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-02-15T03:21:48Z
X-GitHub-Issue: 2311
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2311#issuecomment-2660690692
Content-Type: text/plain; charset=utf-8

Can someone explain why on Earth it is necessary to inform database server about client timezone? What is it used for at the server side? Imagine that my client has timezone Europe/Kurlandia. When it tries to connect to PostgreSQL Server, it gets an error Invalid value for parameter "TimeZone": "Europe/Kurlandia". What exactly does the server fail to do, when it learns that the client has a timezone which is unknown for server's locale libraries?

I do understand how client timezone is used at client side. But I have no idea why database server cares what client timezone is.
Can I just disable those tricky client-timezone-sensitive server features?