From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>, Tan Tran <tankimtran(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GSoC on WAL-logging hash indexes |
Date: | 2014-04-30 18:15:43 |
Message-ID: | CA+TgmoaVJP4Z4wjqGMLCWyc8PKoNE-uRoqTd5P_374GN0ONvmA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers pgsql-students |
On Wed, Apr 30, 2014 at 2:02 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> Of course our current hash indexes have *more* not less contention
>> than btree but I'm pretty comfortable chalking that up to quality of
>> implementation rather than anything intrinsic.
>
> I am not convinced of that.
In commit 76837c1507cb5a5a0048046233568447729e66dd, I remove part
(basically half) of the heavyweight locking used by hash indexes, and
performance improved rather dramatically:
I think it's quite reasonable to suppose that getting rid of the
remaining heavyweight locking will help just as much.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2014-04-30 18:19:33 | Re: GSoC on WAL-logging hash indexes |
Previous Message | Andres Freund | 2014-04-30 18:15:14 | Re: [HACKERS] GSoC on WAL-logging hash indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-04-30 18:18:25 | Re: Fix initdb for path with whitespace and at char |
Previous Message | Andres Freund | 2014-04-30 18:15:14 | Re: [HACKERS] GSoC on WAL-logging hash indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2014-04-30 18:19:33 | Re: GSoC on WAL-logging hash indexes |
Previous Message | Andres Freund | 2014-04-30 18:15:14 | Re: [HACKERS] GSoC on WAL-logging hash indexes |