Re: BUG #14446: make_date with negative year

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: ND Abelisto <abelisto(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14446: make_date with negative year
Date: 2016-12-05 18:57:43
Message-ID: CAFj8pRB1AysgBVtUgT5QHTkvCpjREyCjcou+e6onkPuraheP0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2016-12-05 19:38 GMT+01:00 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:

> Pavel Stehule wrote:
> > 2016-12-04 14:40 GMT+01:00 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
>
> > > abelisto(at)gmail(dot)com wrote:
> > > >
> > > > with t(x) as (values('1111-11-11 BC'::date)) select
> > > make_date(extract(year
> > > > from x)::int, extract(month from x)::int, extract(day from x)::int)
> from
> > > > t;
> > > > ERROR: date field value out of range: -1111-11-11
>
> So make_date was introduced in 9.4 by commit f901bb50e; this report is
> based on 9.5. Do we want to backpatch this change? Since the fix only
> changes behavior that currently errors out anyway, we would not be
> changing anything that people are relying on. I lean towards
> backpatching all the way back to 9.4 myself.
>

I have not a problem with backpatch - there are a user who see current
behave as bug.

Regards

Pavel

>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message rikard 2016-12-06 08:57:36 BUG #14450: inconsistent results on async slave
Previous Message Alvaro Herrera 2016-12-05 18:38:37 Re: BUG #14446: make_date with negative year