Re: GiST nitpicks I want to discuss (and maybe eventually fix)
| От | Michael Banck | 
|---|---|
| Тема | Re: GiST nitpicks I want to discuss (and maybe eventually fix) | 
| Дата | |
| Msg-id | 68e4d4e6.a70a0220.2225bb.6ed7@mx.google.com обсуждение исходный текст  | 
		
| Ответ на | Re: GiST nitpicks I want to discuss (and maybe eventually fix) (Kirill Reshke <reshkekirill@gmail.com>) | 
| Список | pgsql-hackers | 
Hi, On Tue, Oct 07, 2025 at 12:02:21AM +0500, Kirill Reshke wrote: > On Mon, 6 Oct 2025 at 23:53, Andrey Borodin <x4mmm@yandex-team.ru> wrote: > > Makes sense. I hope one day we will add a catalog field to track > > index creation version. This would pave the way to get rid of > > invalid GiST tuples and return this flag too. We can use it for > > something better. > > In the GIN index we have an index creation version, and it is placed > on the metapage. So does btree, if i'm not mistaken . So, the index > version is stored in data, not in catalog. I doubt we will support two > technologies for one purpose. Since GiST index has no metapage, I > doubt we will be successful here. I always found it klunky that you need (AFAIK) an extension (pageinspect) to figure out the btree/gin index version via its meta-page and ISTM that this would be useful information to be stored in the catalog. Michael
В списке pgsql-hackers по дате отправления: