> On 10 Jan 2026, at 19:17, Kirill Reshke <[email protected]> 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()? Best regards, Andrey Borodin.
- Re: GIN pageinspect support for entry tree and posting tree Andrey Borodin
- Re: GIN pageinspect support for entry tree and posting tree Kirill Reshke
- Re: GIN pageinspect support for entry tree and posting tree Kirill Reshke
- Re: GIN pageinspect support for entry tree and posting tree Andrey Borodin
- Re: GIN pageinspect support for entry tree and posting tree Chao Li
- Re: GIN pageinspect support for entry tree and posting tree Kirill Reshke
- Re: GIN pageinspect support for entry tree and posting tree Japin Li
- Re: GIN pageinspect support for entry tree and posting tree Kirill Reshke
- Re: GIN pageinspect support for entry tree and posting tree Japin Li
- Re: GIN pageinspect support for entry tree and posting tree Kirill Reshke
- Re: GIN pageinspect support for entry tree and posting tree Andrey Borodin
- Re: GIN pageinspect support for entry tree and posting tree Japin Li
- Re: GIN pageinspect support for entry tree and posting tree Kirill Reshke
- Re: GIN pageinspect support for entry tree and posting tree Roman Khapov
- Re: GIN pageinspect support for entry tree and posting tree Japin Li
- Re: GIN pageinspect support for entry tree and posting tree Roman Khapov
- Re: GIN pageinspect support for entry tree and posting tree Kirill Reshke
- Re: GIN pageinspect support for entry tree and posting tree Japin Li
- Re: GIN pageinspect support for entry tree and posting tree Andrey Borodin
- Re: GIN pageinspect support for entry tree and posting tree Japin Li
- Re: GIN pageinspect support for entry tree and posting tree Japin Li
