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

From Richard Guo
Subject Re: Assert failure in _bt_preprocess_array_keys
Date
Msg-id CAMbWs4_9c++hqJYd42X8tpWeOeUrZmWPc6O5E_AJhdHLf8UyoQ@mail.gmail.com
Whole thread Raw
In response to Re: Assert failure in _bt_preprocess_array_keys  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers

On Mon, Apr 22, 2024 at 10:52 AM Peter Geoghegan <pg@bowt.ie> wrote:
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.

That's so quick.  Thank you for the prompt fix.

Thanks
Richard

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: ALTER TABLE SET ACCESS METHOD on partitioned tables
Next
From: Michael Paquier
Date:
Subject: Re: Support a wildcard in backtrace_functions