Re: Save Hash Indexes - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Save Hash Indexes
Date
Msg-id 20131101144928.GD9385@awork2.anarazel.de
Whole thread Raw
In response to Re: Save Hash Indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Save Hash Indexes  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
On 2013-11-01 09:49:57 -0400, Tom Lane wrote:
> Lastly: what real-world problem are we solving by kicking that code
> to the curb?

It makes hashed lookups much easier to use. Currently if you want
indexed access over wide columns and equality is all you need you need
to write rather awkward queries to make that happen in each query,
something like:
WHERE hash(column) = hash('value') AND column = 'value'.

So some magic that hides having to do that would be nice, even it
doesn't have O(log(n)) properties. The interesting part is that the
index gets much denser and smaller, and that the individual comparisons
are much cheaper.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: [GENERAL] Cannot create matview when referencing another not-populated-yet matview in subquery
Next
From: Tom Lane
Date:
Subject: Re: API bug in DetermineTimeZoneOffset()