Re: Bad canonicalization for dateranges with 'infinity' bounds

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bad canonicalization for dateranges with 'infinity' bounds
Date: 2019-07-18 20:56:16
Message-ID: d1dc24d791ab173d739824a18308c1b900ab00ad.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 2019-07-14 at 15:27 +1200, Thomas Munro wrote:
> I take back the bit about reading an uninitialised value (X || Y
> doesn't access Y if X is true... duh), but I still think the other
> way
> of putting it is a bit easier to read. YMMV.
>
> Generally, +1 for this patch. I'll wait a couple of days for more
> feedback to appear.

I went ahead and committed this using Thomas's suggestion to remove the
parentheses.

Thanks!

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-07-18 21:36:35 Re: Bad canonicalization for dateranges with 'infinity' bounds
Previous Message Robert Haas 2019-07-18 18:58:31 Re: POC: Cleaning up orphaned files using undo logs