| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: patch: avoid heavyweight locking on hash metapage |
| Date: | 2012-06-26 12:40:30 |
| Message-ID: | CA+TgmoYnzUKJh3=ajsYRv+C_os0pw3R4Dm70V-VF80pPOUFKkA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 25, 2012 at 11:05 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Mon, Jun 18, 2012 at 5:42 PM, Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-06-26 12:43:49 | Re: [PATCH] lock_timeout and common SIGALRM framework |
| Previous Message | Simon Riggs | 2012-06-26 12:35:47 | Re: Catalog/Metadata consistency during changeset extraction from wal |