Learning to hack Postgres - Keeping track of ctids

Поиск
Список
Период
Сортировка
От Emrul
Тема Learning to hack Postgres - Keeping track of ctids
Дата
Msg-id 1475180146617-5923649.post@n3.nabble.com
обсуждение исходный текст
Ответы Re: Learning to hack Postgres - Keeping track of ctids  (Craig Ringer <craig@2ndquadrant.com>)
Re: Learning to hack Postgres - Keeping track of ctids  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Hi,

I'm working on an idea to implement a graph database in Postgres.  At the
moment its just a learning exercise.

What I'd like to do is store a reference to all the links from one record
using an array type that stores links to all related tables.

At first, I've succeeded in doing this using primary key Ids and this works
fine.  However, I'd like to be able to bypass the index lookup altogether by
storing the ctids in my array instead of the primary key ids.

Trouble of course is that ctids can get changed (like for instance
vacuuming).  So my question is: how can I keep my ctid references up to date
- is there any way to detect when a ctid is changed?



--
View this message in context:
http://postgresql.nabble.com/Learning-to-hack-Postgres-Keeping-track-of-ctids-tp5923649.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: pg_basebackup, pg_receivexlog and data durability
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Order of operations in SubPostmasterMain()