Re: GSoC on WAL-logging hash indexes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: GSoC on WAL-logging hash indexes
Date
Msg-id 29533.1398894117@sss.pgh.pa.us
Whole thread Raw
In response to Re: GSoC on WAL-logging hash indexes  (Greg Stark <stark@mit.edu>)
Responses Re: GSoC on WAL-logging hash indexes
List pgsql-hackers
Greg Stark <stark@mit.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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Fix initdb for path with whitespace and at char
Next
From: Robert Haas
Date:
Subject: Re: shm_mq inconsistent behavior of SHM_MQ_DETACHED