From: | Tender Wang <tndrwang(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(at)vondra(dot)me> |
Cc: | 503699317(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org> |
Subject: | Re: BUG #18705: Segmentation fault when create brin index on user-defined type. |
Date: | 2024-11-15 06:17:05 |
Message-ID: | CAHewXNnmBt7xzwhUY1HMQ8Ck=W5T9XJWpQj3qPPhgZcQjBPwNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tomas Vondra <tomas(at)vondra(dot)me> 于2024年11月14日周四 21:48写道:
> On 11/14/24 03:40, PG Bug reporting form wrote:
> > ...
> >
> > CREATE OPERATOR CLASS sva_special_ops FOR TYPE text using brin AS
> OPERATOR 1
> > <#,
> > OPERATOR 2 <=#, OPERATOR 3 >=#, OPERATOR 4 >#, function 1
> > si_same(text,text);
> > CREATE INDEX idx_special1 ON t_sva using brin(sva sva_special_ops);
> >
>
> I think this is a bit confused about CREATE OPERATOR CLASS. For BRIN
> indexes this expects these 4 functions:
>
> Support Function 1 internal function brin_minmax_opcinfo()
> Support Function 2 internal function brin_minmax_add_value()
> Support Function 3 internal function brin_minmax_consistent()
> Support Function 4 internal function brin_minmax_union()
>
> No wonder it crashes if CREATE OPERATOR CLASS passes si_same() instead
> of brin_minmax_opcinfo.
>
Can we report errors not crash if users pass an unexpected function?
--
Thanks,
Tender Wang
From | Date | Subject | |
---|---|---|---|
Next Message | Tender Wang | 2024-11-15 09:10:22 | Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index |
Previous Message | Tom Lane | 2024-11-15 04:25:34 | Re: Sorting Discrepancy in PostgreSQL 14.13 |