Re: BUG #18445: date_part / extract range for hours do not match documentation - Mailing list pgsql-bugs

From Marek Läll
Subject Re: BUG #18445: date_part / extract range for hours do not match documentation
Date
Msg-id CADDPzFRkqATofspRzEBgnMVRUL8-JDu=3OO-DndeQnmKDMAfXg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18445: date_part / extract range for hours do not match documentation  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: BUG #18445: date_part / extract range for hours do not match documentation
Re: BUG #18445: date_part / extract range for hours do not match documentation
List pgsql-bugs
We tend not to introduce breaking changes if the only motivation is to be consistent.
 
Other mistakes are minor, but why is time '24:00:00' allowed, and it's actually 00:00:00 of the next day, that's something I'd like to read a well-argued design decision.
It's like months 1 through 12, and just in case, we also allow month 13, which represents January of the next year. But month 14 is not allowed, which could represent February of the next year.
Could you share the rationale behind this decision?

Marek Läll

pgsql-bugs by date:

Previous
From: "Kumar, Devesh"
Date:
Subject: DETAIL: pg_rewind: servers diverged at WAL location 0/9000000 on timeline 1
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #18445: date_part / extract range for hours do not match documentation