Message-ID: <gh-pgjdbc-pgjdbc-2834-c4055564679@github.com>
From: "motofix (@motofix)" <noreply+motofix@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 13 Mar 2026 14:31:23 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2834: LocalTime.MAX is more precise than postgresql, causing a possible overflow to the next day
In-Reply-To: <gh-pgjdbc-pgjdbc-2834@github.com>
References: <gh-pgjdbc-pgjdbc-2834@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: motofix
X-GitHub-Comment-Id: 4055564679
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2834
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2834#issuecomment-4055564679
Content-Type: text/plain; charset=utf-8

I'm not sure that the issue is specific to `pgjdbc`, as `psql` have the same behaviour:
```none
create table test (
    col timestamp
);

insert into test(col) values ('2023-03-01 00:00:00.000000');
insert into test(col) values ('2023-02-28 23:59:59.999999');

select col from test where col = '2023-02-28 23:59:59.999999999';
         col
---------------------
 2023-03-01 00:00:00
(1 row)
```
Knowing this nanoseconds rounding to microseconds limitation, maybe `pgjdbc` should truncate to microseconds ?