From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: btree_gin: Incorrect leftmost interval value |
Date: | 2023-10-27 14:27:44 |
Message-ID: | 1550349.1698416864@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> 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.
Agreed. When/if the infinite interval patch lands, it could update
this function to use the macro.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2023-10-27 14:46:37 | Re: MERGE ... RETURNING |
Previous Message | Tom Lane | 2023-10-27 14:25:57 | Re: Enderbury Island disappeared from timezone database |