| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tan Tran <tankimtran(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GSoC on WAL-logging hash indexes |
| Date: | 2014-04-30 21:41:57 |
| Message-ID: | 29533.1398894117@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers pgsql-students |
Greg Stark <stark(at)mit(dot)edu> writes:
> But imnsho doing nothing is a bad idea. We should have long ago either
> added WAL logging or removed the index type. We shouldn't have left a
> foot-gun that large lying around for so long.
We can't remove the hash index type, nor move it to an extension,
because it is the operator classes for the built-in hash index AM
that tell the planner and executor how to do hashing for arbitrary
datatypes. And we certainly do not want to give up hashing-based
query plans, whatever you may think of hash indexes.
We really oughta fix the WAL situation, not just band-aid around it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-05-01 19:31:17 | Re: Let's start talking features and "theme" for 9.4 |
| Previous Message | Darren Duncan | 2014-04-30 20:40:55 | Re: [HACKERS] GSoC on WAL-logging hash indexes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-04-30 21:58:25 | Re: shm_mq inconsistent behavior of SHM_MQ_DETACHED |
| Previous Message | Andrew Dunstan | 2014-04-30 21:36:31 | Re: Fix initdb for path with whitespace and at char |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rohit Goyal | 2014-05-12 17:16:16 | Running DBT2 on postgresql |
| Previous Message | Darren Duncan | 2014-04-30 20:40:55 | Re: [HACKERS] GSoC on WAL-logging hash indexes |