Re: BUG #13845: Incorrect week number

On Tue, Jan 5, 2016 at 12:09 PM, Shulgin, Oleksandr <
oleksandr.shulgin@zalando.de> wrote:

> On Tue, Jan 5, 2016 at 11:59 AM, <kees.westerlaken@valuecare.nl> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference:      13845
>> Logged by:          Kees Westerlaken
>> Email address:      kees.westerlaken@valuecare.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.
>

Scratch that, I'm confused about YYYY format, has to use IYYY instead.