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

From Simon Riggs
Subject Re: Fast insertion indexes: why no developments
Date
Msg-id CA+U5nMKhePDSxcwxMNzMYTiHOx94ooydMK6AmCJ15F=zrNq_Pg@mail.gmail.com
Whole thread Raw
In response to Re: Fast insertion indexes: why no developments  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Fast insertion indexes: why no developments  (Robert Haas <robertmhaas@gmail.com>)
Re: Fast insertion indexes: why no developments  (Nicolas Barbier <nicolas.barbier@gmail.com>)
List pgsql-hackers
On 29 October 2013 16:10, Peter Geoghegan <pg@heroku.com> wrote:
> On Tue, Oct 29, 2013 at 7:53 AM, Leonardo Francalanci <m_lists@yahoo.it> wrote:
>> I don't see much interest in insert-efficient indexes.
>
> Presumably someone will get around to implementing a btree index
> insertion buffer one day. I think that would be a particularly
> compelling optimization for us, because we could avoid ever inserting
> index tuples that are already dead when the deferred insertion
> actually occurs.

That's pretty much what the LSM-tree is.

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



pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: Record comparison compiler warning
Next
From: Atri Sharma
Date:
Subject: Re: Handle LIMIT/OFFSET before select clause (was: Feature request: optimizer improvement)