pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: davecramer (@davecramer) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #2311: Why is client time zone not configurable?
Date: Sat, 15 Feb 2025 03:24:22 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Simple,
So that timestamp with time zone will be returned in your time zone
Dave Cramer
On Fri, Feb 14, 2025 at 10:20 PM Сергей Б. ***@***.***> wrote:
> Could anybody 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?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/pgjdbc/pgjdbc/issues/2311#issuecomment-2660690692;,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADDH5TA2NBGI7NAH2GGUAL2P2XBTAVCNFSM6AAAAABVYULISC...;
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
> [image: seregaizsbera]*seregaizsbera* left a comment (pgjdbc/pgjdbc#2311)
> <https://github.com/pgjdbc/pgjdbc/issues/2311#issuecomment-2660690692;
>
> Could anybody 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?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/pgjdbc/pgjdbc/issues/2311#issuecomment-2660690692;,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADDH5TA2NBGI7NAH2GGUAL2P2XBTAVCNFSM6AAAAABVYULISC...;
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
>
view thread (57+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] issue #2311: Why is client time zone not configurable?
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox