Re: Fast insertion indexes: why no developments

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Leonardo Francalanci <m_lists(at)yahoo(dot)it>
Cc: PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fast insertion indexes: why no developments
Date: 2013-11-05 14:58:08
Message-ID: CAGTBQpYyTYo1wq=wZm6xUv9UXonBiZuhOE9FV-2o6XJO6xr_pw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 5, 2013 at 11:28 AM, Leonardo Francalanci <m_lists(at)yahoo(dot)it> wrote:
> I get > 9000 pages for 49 values out of 50... which means scanning 90% of
> the table.
>
> Either my sql is not correct (likely), or my understanding of the minmax
> index is
> not correct (even more likely), or the minmax index is not usable in a
> random inputs
> scenario.

Yep, you're correct. That's the cost for querying random values.

But, both real data isn't truly random, and you haven't really
analyzed update cost, which is what we were talking about in that last
post.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-11-05 15:21:41 Re: logical changeset generation v6.5
Previous Message Tom Lane 2013-11-05 14:55:57 Re: pgsql: Remove internal uses of CTimeZone/HasCTZSet.