On Tue, Feb 18, 2025 at 8:34 AM Laurenz Albe wrote:
> Just for the record: a customer just ran into this bug. REINDEX did
> not fix the bad query result, but update to 17.3 did.
That's surprising, since REINDEX definitely will "fix" my test case
when run on an unpatched server with the bug.
The
On Thu, 2024-12-19 at 11:09 -0500, Peter Geoghegan wrote:
> I should point out (for the benefit of Tom, or whoever writes the next
> set of release notes) that I think that this bug is very unlikely to
> occur in practice. Getting wrong answers to queries could only happen
> given an index with mor
On Wed, Dec 18, 2024 at 3:20 PM Peter Geoghegan wrote:
> Attached fix addresses the issue by consistently resetting the scan's
> so->scanBehind flag (which might still be set to true from the
> previous page's high key) at the start of _bt_advance_array_keys.
I pushed this fix just now.
I should
