From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: Fast GiST index build |
Date: | 2011-07-13 09:16:56 |
Message-ID: | CAPpHfdsOwK+Tbi2oDnKtZ_C+rdzQXfLPuT9CzGFvy+X8Nor+cQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 13, 2011 at 12:40 PM, Alexander Korotkov
<aekorotkov(at)gmail(dot)com>wrote:
> On Wed, Jul 13, 2011 at 12:33 PM, Heikki Linnakangas <
> heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>
>> Is it possible to switch to the new buffering method in the middle of an
>> index build? We could use the plain insertion method until the index grows
>> to a certain size (effective_cache_size?), and switch to the buffering
>> method after that.
>
> Yes, it seems to be possible.
>
It also gives possibility to get estimate of varlena size by real data
before start of buffering method using.
> It also would be great to somehow detect case of ordered data when regular
> index build performs well.
>
I think this case can be detected by the situation when most part of index
tuples are inserting into few leaf pages which was recently used.
------
With best regards,
Alexander Korotkov.
From | Date | Subject | |
---|---|---|---|
Next Message | Nicolas Barbier | 2011-07-13 09:58:58 | Re: Patch Review: Bugfix for XPATH() if text or attribute nodes are selected |
Previous Message | Alexander Korotkov | 2011-07-13 08:40:20 | Re: WIP: Fast GiST index build |