Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: nicolas(dot)maus(at)bertelsmann(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length
Date: 2024-11-06 17:14:56
Message-ID: CAPpHfdsedeW4qiF_Ky88u=+0Ep7ZGH5yBd47a-rueQ2_jh3Dhw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 6, 2024 at 7:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > When extending a varchar column with a gist index with a custom signal
> > length the Postgres server crashes with a segmentation fault.
>
> What this shows is that CompareOpclassOptions has never been tested
> at all except with null inputs. It's trying to call array_eq
> without providing an FmgrInfo.

Thank you for inviting me to the thread. I'm on and will provide a fix shortly.

------
Regards,
Alexander Korotkov
Supabase

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Davis 2024-11-06 17:35:27 17: lc_collate_is_c() when LC_CTYPE != LC_COLLATE
Previous Message Tom Lane 2024-11-06 17:08:53 Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length