Re: Bad canonicalization for dateranges with 'infinity' bounds

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bad canonicalization for dateranges with 'infinity' bounds
Date: 2019-07-19 00:17:03
Message-ID: 263c516302e7afbd982b14f37629bc2601e15281.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2019-07-18 at 17:36 -0400, Tom Lane wrote:
> The commit message claims this was back-patched, but I see no back-
> patch?

Sorry, I noticed an issue after pushing: we were passing a datum
directly to DATE_NOT_FINITE, when we should have called
DatumGetDateADT() first. I ran through the tests again and now pushed
to all branches.

> (The commit message doesn't seem to have made it to the pgsql-
> committers
> list either, but that's probably an independent issue.)

I was curious about that as well.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-07-19 00:19:19 Re: Bad canonicalization for dateranges with 'infinity' bounds
Previous Message Ian Barwick 2019-07-19 00:04:03 Re: Documentation fix for adding a column with a default value