Re: Concurrence GiST - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Concurrence GiST
Date
Msg-id 40302BE2.8040301@familyhealth.com.au
Whole thread Raw
In response to Concurrence GiST  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Concurrence GiST  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Hey Teodor,

How's this going?

I think you were looking at the same paper I was reading about GiST 
indexes.  I found the GiST source code somewhat over my head, however.

I hope you'll still working on it and haven't given up!

Chris

Teodor Sigaev wrote:

> 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?
> 
> 
> 
> 


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: No Timeout in SELECT..FOR UPDATE
Next
From: Teodor Sigaev
Date:
Subject: Re: Concurrence GiST