Re: patch: avoid heavyweight locking on hash metapage - Mailing list pgsql-hackers

From Robert Haas
Subject Re: patch: avoid heavyweight locking on hash metapage
Date
Msg-id CA+TgmoYnzUKJh3=ajsYRv+C_os0pw3R4Dm70V-VF80pPOUFKkA@mail.gmail.com
Whole thread Raw
In response to Re: patch: avoid heavyweight locking on hash metapage  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On Mon, Jun 25, 2012 at 11:05 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> On Mon, Jun 18, 2012 at 5:42 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>
>> Hmm.  That was actually a gloss I added on existing code to try to
>> convince myself that it was safe; I don't think that the changes I
>> made make that any more or less safe than it was before.
>
> Right, sorry.  I thought there was some strength reduction going on
> there as well.
>
> Thanks for the various explanations, they address my concerns.  I see
> that v2 applies over v1.
>
> I've verified performance improvements using 8 cores with my proposed
> pgbench -P benchmark, with a scale that fits in shared_buffers.
> It brings it most of the way, but not quite, up to the btree performance.
>
>
> I've marked this as ready for committer.

Thanks for the review; committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Catalog/Metadata consistency during changeset extraction from wal
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] lock_timeout and common SIGALRM framework