Re: btree_gin: Incorrect leftmost interval value
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-10-27T14:27:44Z
Lists: pgsql-hackers
Dean Rasheed <dean.a.rasheed@gmail.com> writes: > On Fri, 27 Oct 2023 at 13:56, Ashutosh Bapat > <ashutosh.bapat.oss@gmail.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
Commits
-
btree_gin: Fix calculation of leftmost interval value.
- 849172ff4883 17.0 landed
- ab73a37e9e1e 16.1 landed
- 5f06918399f0 15.5 landed
- 35e6a5c20d45 13.13 landed
- 162b38a06839 14.10 landed
- f7cd7b265f6f 12.17 landed
- c804ffb5622b 11.22 landed