Re: Learning to hack Postgres - Keeping track of ctids
От | Craig Ringer |
---|---|
Тема | Re: Learning to hack Postgres - Keeping track of ctids |
Дата | |
Msg-id | CAMsr+YFRYXpB8cV+V3TLhAYhn=RQB0KmvMhwjOVdBpCP8itkrQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Learning to hack Postgres - Keeping track of ctids (Emrul <emrul@emrul.com>) |
Список | pgsql-hackers |
<p dir="ltr"><p dir="ltr">On 30 Sep. 2016 19:36, "Emrul" <<a href="mailto:emrul@emrul.com">emrul@emrul.com</a>> wrote:<br/> ><br /> > Thanks Craig, I will look at that code.<br /> ><br /> > The alternative I'm consideringis whether I can define my own index type on<br /> > the column storing my array of primary key ids. The indexwould, for each<br /> > primary key id just provide a reference to the ctids of the related records.<br /> ><br/> > In theory, I think this might be less work. However, I am yet to find a<br /> > simple/bare index implementationthat I can build upon.<p dir="ltr">I don't think indexes are fully pluggable yet. And I'd be surprised if itwere possible within GiST /GIN. Check out the 9.6 / v10 pg_am changes, which I think may be relevant.<p dir="ltr">Or itcould be an unrelated dead end because I know little about indexing.<p dir="ltr">><br /> ><br /> ><br /> >--<br /> > View this message in context: <a href="http://postgresql.nabble.com/Learning-to-hack-Postgres-Keeping-track-of-ctids-tp5923649p5923757.html">http://postgresql.nabble.com/Learning-to-hack-Postgres-Keeping-track-of-ctids-tp5923649p5923757.html</a><br />> Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.<br /> ><br /> ><br /> > --<br /> >Sent via pgsql-hackers mailing list (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br/> > To make changes to your subscription:<br/> > <a href="http://www.postgresql.org/mailpref/pgsql-hackers">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/>
В списке pgsql-hackers по дате отправления: