| From: | Jingtang Zhang <mrdrivingduck(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19664: nbtree: Assertion failure when a custom index AM reuses bthandler |
| Date: | 2026-09-10 06:30:14 |
| Message-ID: | CAPsk3_B2Xd5xXcxMtTd1Budnz4=HzGWYBJNsMA2Lfq9+SOOdzQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi, Andrey Borodin
Thanks for the explanation.
> The gist2 regression case is a test hack, not a documented interface. I
> therefore don't think removing this one Assert would make this usage
> valid. The assertion failure could perhaps be replaced with a regular
> error instead.
What is the intended scope of reusing built-in AM handlers through
CREATE ACCESS METHOD? Is this something we aim to support, or should
extensions provide their own handlers even when reusing an existing
implementation?
The gist2 regression test made me wonder where that boundary lies,
particularly for bthandler. If this usage is not supported, would a
regular error be more appropriate than an assertion failure?
---
Best regards,
Jingtang Zhang
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Rachitskiy | 2026-09-10 07:56:47 | Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation |
| Previous Message | Andrey Rachitskiy | 2026-09-10 05:36:46 | Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation |