From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Subject: | Re: GiST: memory allocation, cleanup |
Date: | 2004-11-06 00:31:07 |
Message-ID: | 418C1B4B.5000609@samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Alvaro Herrera wrote:
> What are you going to base your concurrency work on? I wonder because I
> skimmed through Marcel Kornacker's theses, and for example it mentioned
> use of predicate locking (among other interesting things). Do you have
> any ideas yet on how to handle that?
I've read a paper[1] on concurrency and recovery by Kornacker, C. Mohan
and Hellerstein, which is presumably pretty close to Kornacker's thesis
work (which I'll definitely read later). My understanding is that
there's no need to implement predicate locking for GiST any more than
for B+-trees -- it's a nice feature to prevent phantoms, but not a
requirement for implementing page-level concurrency. So I haven't given
any thought to implementing it. If I've misunderstood, please let me know.
-Neil
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Bertheau | 2004-11-06 00:36:59 | Re: contrib/xml2: add function xml_encode_special_chars |
Previous Message | Peter Eisentraut | 2004-11-06 00:24:09 | Re: contrib/xml2: add function xml_encode_special_chars |