Re: btree_gin: Incorrect leftmost interval value

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: btree_gin: Incorrect leftmost interval value
Date: 2023-10-27 13:05:21
Message-ID: CAEZATCVU+vps5s2x-FWpz1=qYZ_Jnv87SV6xbuVG1whMRAbSPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 27 Oct 2023 at 13:56, Ashutosh Bapat
<ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> wrote:
>
> Should we change this to call INTERVAL_NOBEGIN() to be added by
> infinite interval patches?
>

Given that this is a bug that can lead to incorrect query results, I
plan to back-patch it, and INTERVAL_NOBEGIN() wouldn't make sense in
back-branches that don't have infinite intervals.

Regards,
Dean

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2023-10-27 13:20:09 Re: Reducing connection overhead in pg_upgrade compat check phase
Previous Message Ashutosh Bapat 2023-10-27 12:56:14 Re: btree_gin: Incorrect leftmost interval value