Re: Ignore hash indices on replicas

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Steven Schlansker <steven(at)likeness(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Ignore hash indices on replicas
Date: 2012-08-20 17:55:08
Message-ID: CAMkU=1xL_dM8ONK1390iR_aOtQMkG1GrGGppEQRuytmw4Us7cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Aug 20, 2012 at 10:29 AM, Steven Schlansker <steven(at)likeness(dot)com> wrote:
>
> On Aug 19, 2012, at 2:37 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>
>> On Tue, 2012-07-10 at 00:09 -0700, Steven Schlansker wrote:
>>> show that our particular application is faster by quite a bit when a
>>> hash index is available.
>>
>> Can you publish the results somewhere? It might provoke some interest.
>
> I might be able to spend some time looking at making this public, but the general parameters are:
>
> 122M rows, lookup key is a UUID type. Lookups are ~1000 random keys at a time (as in, a giant SELECT * FROM table WHERE key IN (?,?,?,?,…)

How well cached is the data?

If it has to be read from disk, then a bitmap index scan on a btree
index with effective_io_concurrency set high might do quite well,
assuming you can convince the planner to use one.

Cheers,

Jeff

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Johnston 2012-08-20 18:09:48 Re: Database Bloat
Previous Message elliott 2012-08-20 17:53:47 Database Bloat