From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling |
Date: | 2004-08-24 07:36:21 |
Message-ID: | 412AEFF5.2010306@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2004-08-24 08:05:20 | Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling |
Previous Message | Tom Lane | 2004-08-24 05:38:17 | Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling |
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB SD | 2004-08-24 07:43:45 | Re: PITR: XLog File compression on Archive |
Previous Message | Simon Riggs | 2004-08-24 07:28:47 | Re: PITR: XLog File compression on Archive |