| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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-06-30 22:28:17 |
| Message-ID: | BANLkTinUyGQP5ApN3=KmQ4AAUKdBjvCjhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27 June 2011 15:13, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I didn't get a lot of comments on my the previous version of my patch
> to accelerate table locks.
>
> http://archives.postgresql.org/pgsql-hackers/2011-06/msg00953.php
>
> Here's a new version anyway. In this version, I have:
>
> 1. Made pg_locks show fast-path locks as well as regular locks, with a
> new Boolean column to distinguish.
> 2. Renamed fpLWLock to backendLock, on the belief that we're going to
> want something like this for quite a bit more than just this one
> patch.
> 3. Removed some debugging code.
Are you able to benchmark this again, and possibly get Stefan to give
it a go too?
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2011-06-30 22:35:40 | Re: add support for logging current role (what to review?) |
| Previous Message | Jeff Davis | 2011-06-30 22:19:09 | Re: [COMMITTERS] pgsql: Make the visibility map crash-safe. |