Re: Assert failure in _bt_preprocess_array_keys

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Assert failure in _bt_preprocess_array_keys
Date: 2024-04-22 02:52:16
Message-ID: CAH2-WznLUb4nSVnrbE4Ur86U-NjCEJx8JkuPLbssT68YueVbjQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 21, 2024 at 10:36 PM Richard Guo <guofenglinux(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2024-04-22 03:51:02 Re: POC: GROUP BY optimization
Previous Message Richard Guo 2024-04-22 02:36:13 Assert failure in _bt_preprocess_array_keys