Concurrence GiST

Hi!

I'll have time and wish to work on concurrence GiST during january.
Now I am reading some paper about this and looking into code of postgres for 
lock management. As I see, postgres doesn't support intentional lock. Is it 
right? or I missed something...

I can use NSN (node sequence number) and I find recommendation to use LSN (WAL 
log sequence number) as NSN. NSN must be stored in page and I found that  page 
(PageHeaderData struct) already has XLogRecPtr for storing LSN. My question is: 
who is manage this field? Is it filled automatically or I should write code to 
manage it?




-- 
Teodor Sigaev                                  E-mail: teodor@sigaev.ru