Re: Assert failure in _bt_preprocess_array_keys - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Assert failure in _bt_preprocess_array_keys
Date
Msg-id CAH2-WznLUb4nSVnrbE4Ur86U-NjCEJx8JkuPLbssT68YueVbjQ@mail.gmail.com
Whole thread Raw
In response to Assert failure in _bt_preprocess_array_keys  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: Assert failure in _bt_preprocess_array_keys
List pgsql-hackers
On Sun, Apr 21, 2024 at 10:36 PM Richard Guo <guofenglinux@gmail.com> wrote:
> I didn't spend much time digging into it, but I wonder if this Assert is
> sensible.  I noticed that before commit 5bf748b86b, the two datatypes
> were not equal to each other either (anyrange vs. int4range).

The assertion is wrong. It is testing behavior that's much older than
commit 5bf748b86b, though. We can just get rid of it, since all of the
information that we'll actually apply when preprocessing scan keys
comes from the operator class.

Pushed a fix removing the assertion just now. Thanks for the report.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Assert failure in _bt_preprocess_array_keys
Next
From: Andrei Lepikhov
Date:
Subject: Re: POC: GROUP BY optimization