Re: Fast insertion indexes: why no developments - Mailing list pgsql-hackers

From Nicolas Barbier
Subject Re: Fast insertion indexes: why no developments
Date
Msg-id CAP-rdTYWGj96v9zJr=ZMXxw8Uf6c5hhQ4jA0waas8zLDW4PmPA@mail.gmail.com
Whole thread Raw
In response to Re: Fast insertion indexes: why no developments  (Nicolas Barbier <nicolas.barbier@gmail.com>)
List pgsql-hackers
2013/11/12 Nicolas Barbier <nicolas.barbier@gmail.com>:

> In conclusion, use a “B-forest” when:
>
> * The index entries are small (large fan-out).
> * The insertion throughput is high.
> * It’s OK for look-ups to be slow.
> * Extra points when the storage medium has high seek times.

Oops, forgot the most important ones:

* Insertions are random.
* The total amount of data is very high.

Nicolas

--
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?



pgsql-hackers by date:

Previous
From: David Johnston
Date:
Subject: Re: Transaction-lifespan memory leak with plpgsql DO blocks
Next
From: Simon Riggs
Date:
Subject: Re: Fast insertion indexes: why no developments