Re: Batch update of indexes

From: konstantin knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Batch update of indexes
Date: 2016-02-04 07:37:27
Message-ID: 4B974F4C-87DE-46BE-A721-D341296512D3@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Feb 4, 2016, at 2:00 AM, Jim Nasby wrote:

>
> My suspicion is that it would be useful to pre-order the new data before trying to apply it to the indexes.

Sorry, but ALTER INDEX is expected to work for all indexes, not only B-Tree, and for them sorting may not be possible...
But for B-Tree presorting inserted data should certainly increase performance.
I will think about it.

> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Experts in Analytics, Data Architecture and PostgreSQL
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2016-02-04 07:43:19 Re: pg_dump data structures for triggers
Previous Message Kouhei Kaigai 2016-02-04 06:30:25 Re: Way to check whether a particular block is on the shared_buffer?