| From: | Tender Wang <tndrwang(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-07 06:47:42 |
| Message-ID: | CAHewXN=eBAk2wMn00CCYqcqC-1UtCHBMxr0nREUp_Ch8XYSQEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi all,
Alexander Korotkov <aekorotkov(at)gmail(dot)com> 于2024年11月7日周四 01:15写道：
> 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.
>
>
Based on Tom's analysis, I provide a POC patch. I'm not sure if it is right
to use DEFAULT_COLLATION_OID in the patch.
--
Thanks,
Tender Wang
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Try-to-fix-array_eq-without-providing-FmgrInfo-issue.patch | application/octet-stream | 1.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2024-11-07 08:32:30 | TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' |
| Previous Message | Jan Behrens | 2024-11-07 01:23:44 | Re: BUG #18693: Column names not set when using SELECT STRICT INTO with RECORD type |