Message-ID: <gh-pgjdbc-pgjdbc-3482-c2599014658@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 17 Jan 2025 19:03:07 +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: 2599014658
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-2599014658
Content-Type: text/plain; charset=utf-8

Well your bug shows the problem. 
We do need to handle timestamps better, it's just not been addressed.
I do think it is a postgres problem, at least there's nothing we can do from a driver perspective.
The pl block probably binds it to a specific type. I would have to look at the code. PL/Pgsql runs in the server, not through the protocol so it has more information.

As for the two types, yes one with TZ and one without. There are oddities with TZ. The data is actually stored at UTC and converted to the client timezone.

Cheers,
Dave