Message-ID: <gh-pgjdbc-pgjdbc-3482-c2602191029@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 20 Jan 2025 11:37:47 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3482: When using java.sql.Timestamp for update, an exception thrown
In-Reply-To: <gh-pgjdbc-pgjdbc-3482@github.com>
References: <gh-pgjdbc-pgjdbc-3482@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2602191029
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3482
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3482#issuecomment-2602191029
Content-Type: text/plain; charset=utf-8

So I was able to confirm your assertion that it could be fixed in the driver. That said you've run into another problem which I eluded to earlier. The reason we send it in text is because we don't know if you want Timestamp with or without TZ so we send it as text and let the server figure it out. In this case the server can't figure it out. 
I'm open to suggestions, however please look at the history of this discussion, there are quite a few issues and PR's referring to timestamp. If only the spec supported 2 timestamps