Re: GIN pageinspect support for entry tree and posting tree
| От | Kirill Reshke |
|---|---|
| Тема | Re: GIN pageinspect support for entry tree and posting tree |
| Дата | |
| Msg-id | CALdSSPg6cqqWNDkAWX0RfB7CXM+oxacHivHPa90dZtX27KBGLg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: GIN pageinspect support for entry tree and posting tree (Japin Li <japinli@hotmail.com>) |
| Ответы |
Re: GIN pageinspect support for entry tree and posting tree
|
| Список | pgsql-hackers |
On Wed, 14 Jan 2026 at 07:19, Japin Li <japinli@hotmail.com> wrote: > > On Sun, 11 Jan 2026 at 21:43, Andrey Borodin <x4mmm@yandex-team.ru> wrote: > >> On 10 Jan 2026, at 19:17, Kirill Reshke <reshkekirill@gmail.com> wrote: > >> > >> So, > >> v14-0004 with this change attached. > > > > Did you mean 0003? > > > > The change makes sense, but I'd note that macro is always used like this: > > > > if (!IS_INDEX(indexRel) || !IS_HASH(indexRel)) > > > > If we are refactoring this, maybe put IS_INDEX inside of corresponding IS_BTREE(),IS_GIN() and IS_HASH()? > > > > +1 > > Attach the v15 patch. > v15-0001 and v15-0002 unchanged and v15-0003 changed as above. > > -- > Regards, > Japin Li > ChengDu WenWu Information Technology Co., Ltd. > Hi! Thank you 🙏 for your effort. 0003 looks good to me -- Best regards, Kirill Reshke
В списке pgsql-hackers по дате отправления: