From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GSoC proposal: Fast GiST index build |
Date: | 2011-04-04 16:50:03 |
Message-ID: | BANLkTikCOeEXGFxp4O7zVoYcrpFSuTn7SA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 4, 2011 at 12:46 PM, Alexander Korotkov
<aekorotkov(at)gmail(dot)com> wrote:
> On Mon, Apr 4, 2011 at 7:04 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>
>> On Mon, Apr 4, 2011 at 7:16 AM, Alexander Korotkov <aekorotkov(at)gmail(dot)com>
>> wrote:
>> > Project name
>> > Fast GiST index build
>>
>> Would/could/should this be implemented in a manner similar to the
>> existing "GIN fast update" feature?
>
> I've mentioned this problem in item #2 in project details. In short. Problem
> is in concurrent selects. Buffers size is significant and their scan in
> concurrent select can cause significant slow down. Probably, compromise can
> be achived by using for smaller buffers or something like this, but it's
> topic of separate research. It doesn't seems to be feasible for me to give a
> production solution of this problem during GSoC.
OK. Could you briefly describe the algorithm you propose to
implement, bearing in mind that I haven't read the paper?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-04-04 17:01:38 | Re: Proposal: q-gram GIN and GiST indexes |
Previous Message | Robert Haas | 2011-04-04 16:47:18 | Re: Re: [COMMITTERS] pgsql: Support comments on FOREIGN DATA WRAPPER and SERVER objects. |