Re: WIP: Fast GiST index build
От | Alexander Korotkov |
---|---|
Тема | Re: WIP: Fast GiST index build |
Дата | |
Msg-id | CAPpHfdszFQ7KyWurN7+AMSdG-v4m-p=HgpLPH=XUZqbnGJf+og@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: WIP: Fast GiST index build (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: WIP: Fast GiST index build
|
Список | pgsql-hackers |
<div class="gmail_quote">Fri, Jul 15, 2011 at 12:53 AM, Heikki Linnakangas <span dir="ltr"><<a href="mailto:heikki.linnakangas@enterprisedb.com">heikki.linnakangas@enterprisedb.com</a>></span>wrote:<br /><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On14.07.2011 23:41, Alexander Korotkov wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px#ccc solid;padding-left:1ex"> Do you think using "rightlink" as pointer to parent page is possible during<br/> index build? It would allow to simplify code significantly, because of no<br /> more need to maintain in-memorystructures for parents memorizing.<br /></blockquote><br /></div> I guess, but where do you store the rightlink,then? Would you need a final pass through the index to fix all the rightlinks?<br /><br /> I think you could usethe NSN field. It's used to detect concurrent page splits, but those can't happen during index build, so you don't needthat field during index build. You just have to make it look like an otherwise illegal NSN, so that it won't be mistakenfor a real NSN after the index is built. Maybe add a new flag to mean that the NSN is actually invalid.</blockquote><divclass="gmail_quote"><br /></div><div class="gmail_quote">Thank you for advice. But I didn't takeinto account that in this case I need to update parent link in many pages(which might be not in cache) on split. Seemsthat I still need to maintain some in-memory structures for parent finding.</div><br />------<br />With best regards,<br/>Alexander Korotkov.</div>
В списке pgsql-hackers по дате отправления: