| From: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | kees(dot)westerlaken(at)valuecare(dot)nl |
| Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13845: Incorrect week number |
| Date: | 2016-01-05 11:09:04 |
| Message-ID: | CACACo5RY7TK4C7hVBKX1-C=BZgmY6D3rnTKMcAhYO=J+CFwNWg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jan 5, 2016 at 11:59 AM, <kees(dot)westerlaken(at)valuecare(dot)nl> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13845
> Logged by: Kees Westerlaken
> Email address: kees(dot)westerlaken(at)valuecare(dot)nl
> PostgreSQL version: 9.2.10
> Operating system: Linux
> Description:
>
> 2016 is a year where week numbers (US) differ from ISO.
>
> On 1 januari 2016 it works OK.
> select to_char(to_date('20160101', 'YYYYMMDD'), 'YYYYWW')
> produces 201601, while
> select to_char(to_date('20160101', 'YYYYMMDD'), 'YYYYIW')
> produces 201553.
>
It gets worse on HEAD:
postgres=# select to_char(to_date('20160101', 'YYYYMMDD'), 'YYYY:IW');
to_char
---------
2016:53
(1 row)
This is something close to 2017 already.
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shulgin, Oleksandr | 2016-01-05 11:11:54 | Re: BUG #13845: Incorrect week number |
| Previous Message | kees.westerlaken | 2016-01-05 10:59:24 | BUG #13845: Incorrect week number |