From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Concurrence GiST |
Date: | 2004-02-16 02:33:06 |
Message-ID: | 40302BE2.8040301@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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?
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | news.postgresql.org | 2004-02-16 03:29:42 | CHAR(n) always trims trailing spaces in 7.4 |
Previous Message | Andrew Dunstan | 2004-02-16 02:16:21 | Re: [PATCHES] dollar quoting |