Re: BUG #14446: make_date with negative year - Mailing list pgsql-bugs

From Pavel Stehule
Subject Re: BUG #14446: make_date with negative year
Date
Msg-id CAFj8pRB1AysgBVtUgT5QHTkvCpjREyCjcou+e6onkPuraheP0Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14446: make_date with negative year  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [BUGS] BUG #14446: make_date with negative year
List pgsql-bugs
2016-12-05 19:38 GMT+01:00 Alvaro Herrera <alvherre@2ndquadrant.com>:

> Pavel Stehule wrote:
> > 2016-12-04 14:40 GMT+01:00 Alvaro Herrera <alvherre@2ndquadrant.com>:
>
> > > abelisto@gmail.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

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

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #14446: make_date with negative year
Next
From: rikard@ngs.hr
Date:
Subject: BUG #14450: inconsistent results on async slave