Message-ID: <263c516302e7afbd982b14f37629bc2601e15281.camel@j-davis.com>
Subject: Re: Bad canonicalization for dateranges with 'infinity' bounds
From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>, Laurenz Albe
	 <laurenz.albe@cybertec.at>, PostgreSQL Hackers
	 <pgsql-hackers@lists.postgresql.org>
Date: Thu, 18 Jul 2019 17:17:03 -0700
In-Reply-To: <16949.1563485795@sss.pgh.pa.us>
References: <77f24ea19ab802bc9bc60ddbb8977ee2d646aec1.camel@cybertec.at>
	 <539fbfe416eb3d7ebf72268eb839163a68aed9ef.camel@cybertec.at>
	 <CA+hUKGJ0gUs-BMRwCgQF-dtURq_7aT1Ecum22u2jH2CcdEQAYw@mail.gmail.com>
	 <CA+hUKGLvizV-pTaSkGbCPJVGyH4Rex+KEnYEOZvPfsKyiogXpg@mail.gmail.com>
	 <d1dc24d791ab173d739824a18308c1b900ab00ad.camel@j-davis.com>
	 <16949.1563485795@sss.pgh.pa.us>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

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