Re: What does Time.MAX_VALUE actually represent? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: What does Time.MAX_VALUE actually represent?
Date
Msg-id 0d31a5de-c1c4-4c24-38ee-196faab9d061@2ndquadrant.com
Whole thread Raw
In response to What does Time.MAX_VALUE actually represent?  (Dave Cramer <davecramer@gmail.com>)
Responses Re: What does Time.MAX_VALUE actually represent?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12/30/17 09:07, Dave Cramer wrote:
> We are having a discussion on the jdbc project about dealing with 24:00:00.
> 
> https://github.com/pgjdbc/pgjdbc/pull/992#issuecomment-354507612

select timestamp '2017-12-30 24:00:00';

returns

2017-12-31 00:00:00

which makes some sense.

I don't know why we accept that and not '24:00:01' and beyond, but it's
probably historical.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Bear Giles
Date:
Subject: Re: What does Time.MAX_VALUE actually represent?
Next
From: Ivan Kartyshov
Date:
Subject: [Patch] Checksums for SLRU files