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+U5nMLRTviShk4AE+m=sVYak0AmFLa7uJ8mi+wztJ0M2=NCvA@mail.gmail.com
Whole thread Raw
In response to Re: Fast insertion indexes: why no developments  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On 13 November 2013 11:54, Merlin Moncure <mmoncure@gmail.com> wrote:

>> Load time
>> MinMax no overhead, same as raw COPY
>> BTree - considerably slower

And just as a general comment, the min max index does not slow down
COPY as the table gets larger, whereas the btree gets slower as the
table gets larger. Which is the reason Leonardo requires partitioned
tables.

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



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Idea for debug/recovery snapshots
Next
From: Bruce Momjian
Date:
Subject: Re: Add \i option to bring in the specified file as a quoted literal