Re: BUG #14446: make_date with negative year

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: 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:38:37
Message-ID: 20161205183837.dcs5y3sfoiwgv6b3@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

--
Á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 Pavel Stehule 2016-12-05 18:57:43 Re: BUG #14446: make_date with negative year
Previous Message David G. Johnston 2016-12-05 18:30:39 Re: BUG #14449: inconsistency in behaviour of json/jsonb returning functions for sql NULL and json NULL values