| From: | Marek Läll <lall(dot)marek(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "fcaldasdesou(at)bloomberg(dot)net" <fcaldasdesou(at)bloomberg(dot)net>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18445: date_part / extract range for hours do not match documentation |
| Date: | 2024-04-26 19:27:49 |
| Message-ID: | CADDPzFRkqATofspRzEBgnMVRUL8-JDu=3OO-DndeQnmKDMAfXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-04-26 19:36:30 | Re: BUG #18445: date_part / extract range for hours do not match documentation |
| Previous Message | Kumar, Devesh | 2024-04-26 19:06:56 | DETAIL: pg_rewind: servers diverged at WAL location 0/9000000 on timeline 1 |