I think the speed complaint I was just raising could possibly be answered by setting an infomask bit indicating that the row might be present in a separate table of active row locks. (I'm not sure how the bit would get cleared without race conditions, but let's suppose that can be done.) A little hashing, a little spill-to-disk logic, and it might be done. But that's just handwaving... anyone want to try to fill in the details?
I vote Alvaro :) This stuff is way out of my league - I'm just the ideas man :D
Either way - Bruce, did you want to add a summary of these ideas to the TODO?
Chris
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
