| From: | Florian Weimer <fweimer(at)bfk(dot)de> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, pgsql-hackers(at)postgresql(dot)org, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Subject: | Re: reducing the overhead of frequent table locks, v4 |
| Date: | 2011-07-11 11:25:01 |
| Message-ID: | 82hb6tukj6.fsf@mid.bfk.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Jeff Davis:
> Does this happen to be based on some academic research? I don't
> necessarily expect it to be; just thought I'd ask.
Paul E. McKenney's thesis contains a few references. It's called
"asymmetrical reader-writer locking" there, and Ingo Molnar implemented
this as "brlock" in Linux 2.4. The earliest citation seems to be
W.C. Hsiesh, W. E. Weihl, "Scalable reader-writer locks for parallel
systems.", MIT-LCS-TR-521, published in 1991.
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2011-07-11 13:10:57 | Re: [HACKERS] Creating temp tables inside read only transactions |
| Previous Message | Florian Pflug | 2011-07-11 08:15:02 | Re: Need help understanding pg_locks |