public inbox for [email protected]
help / color / mirror / Atom feedFrom: Richard Guo <[email protected]>
To: Peter Geoghegan <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Assert failure in _bt_preprocess_array_keys
Date: Mon, 22 Apr 2024 14:22:25 +0800
Message-ID: <CAMbWs4_9c++hqJYd42X8tpWeOeUrZmWPc6O5E_AJhdHLf8UyoQ@mail.gmail.com> (raw)
In-Reply-To: <CAH2-WznLUb4nSVnrbE4Ur86U-NjCEJx8JkuPLbssT68YueVbjQ@mail.gmail.com>
References: <CAMbWs48f5rDOwxaT76Zd40m7n9iGZQcjEk7vG_5p3YWNh6oPfA@mail.gmail.com>
<CAH2-WznLUb4nSVnrbE4Ur86U-NjCEJx8JkuPLbssT68YueVbjQ@mail.gmail.com>
On Mon, Apr 22, 2024 at 10:52 AM Peter Geoghegan <[email protected]> wrote:
> On Sun, Apr 21, 2024 at 10:36 PM Richard Guo <[email protected]>
> 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
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Assert failure in _bt_preprocess_array_keys
In-Reply-To: <CAMbWs4_9c++hqJYd42X8tpWeOeUrZmWPc6O5E_AJhdHLf8UyoQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox