From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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:19:33 |
Message-ID: | CAM3SWZR_Xmc=ZgRJdK-JRm7OxHvCUKgdL=DVNBOs1YxOTr-1Aw@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 11:03 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> If we don't put in the work to make them useful, then they won't ever become
> useful.
>
> If we do put in the effort (and it would be considerable) then I think they
> will be. But you may be correct that the effort required would perhaps be
> better used in making btree even more better. I don't think we can conclude
> that definitively without putting in the work to do the experiment.
My argument doesn't hinge on there being more important work to do.
Rather, I simply don't think that there is never going to be a
compelling reason to use hash indexes in production. Apart from the
obvious inflexibility, consider what it takes to make index creation
fast - insertion-style building of indexes is much slower. Consider
multi-key indexes.
Now, I'm not telling anyone what to work on, and if someone wants to
make hash indexes WAL-logged to plug that hole, don't let me stop you.
It probably makes sense as a project to learn more about Postgres
internals. However, it would be unfair to not speak up given my
misgivings around the practical utility of hash indexes.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2014-04-30 19:16:53 | Re: GSoC on WAL-logging hash indexes |
Previous Message | Robert Haas | 2014-04-30 18:15:43 | Re: GSoC on WAL-logging hash indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-04-30 19:03:06 | Re: Fix initdb for path with whitespace and at char |
Previous Message | Tom Lane | 2014-04-30 18:18:25 | Re: Fix initdb for path with whitespace and at char |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2014-04-30 19:16:53 | Re: GSoC on WAL-logging hash indexes |
Previous Message | Robert Haas | 2014-04-30 18:15:43 | Re: GSoC on WAL-logging hash indexes |