From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Peter Geoghegan <peter@2ndquadrant.com>
Cc: Stefan Keller <sfkeller@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hash index use presently(?) discouraged since 2005: revive or bury it?
Date: Thu, 15 Sep 2011 18:38:08 -0400
Message-ID: <13742.1316126288@sss.pgh.pa.us> (raw)
In-Reply-To: <CAHyXU0w3e1reYpebLU93bdhwJFpRkdGBz9FhXWFW6s-Bb0sp5g@mail.gmail.com>
References: <CAFcOn293Rzi7cZYWBT8tjxCtNX5pYdbknANXgf9mWfBizK8Frg@mail.gmail.com>
<CAEYLb_Udue8_XSE9K0KMqKBE_62yurv1bY4Wc+qJoGykZ_rXtA@mail.gmail.com>
<16096.1315959870@sss.pgh.pa.us>
<4E706DFE.40801@enterprisedb.com>
<CAHyXU0w3e1reYpebLU93bdhwJFpRkdGBz9FhXWFW6s-Bb0sp5g@mail.gmail.com>
Merlin Moncure <mmoncure@gmail.com> writes:
> HM, what if you junked the current hash indexam, and just implemented
> a wrapper over btree so that the 'hash index' was just short hand for
> hashing the value into a standard index?
Surely creating such a wrapper would be *more* work than adding WAL
support to the hash AM.
I'm not entirely following this eagerness to junk that AM, anyway.
We've put a lot of sweat into it over the years, in the hopes that
it would eventually be good for something. It's on the edge of
being good for something now, and there's doubtless room for more
improvements, so why are the knives out?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, mmoncure@gmail.com, heikki.linnakangas@enterprisedb.com, peter@2ndquadrant.com, sfkeller@gmail.com
Subject: Re: Hash index use presently(?) discouraged since 2005: revive or bury it?
In-Reply-To: <13742.1316126288@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox