Re: [PATCHES] GIN improvements

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] GIN improvements
Date: 2008-12-02 14:11:01
Message-ID: 493541F5.2020401@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Teodor Sigaev wrote:
> - Falling back to regular insert will take long time for update of whole
> table - and that was one of reasons of that patch. Users forget to drop
> GIN index before a global update and query runs forever.

If *that* is a use case we're interested in, the incoming tuples could
be accumulated in backend-private memory, and inserted into the index at
commit. That would be a lot simpler, with no need to worry about
concurrent inserts or vacuums.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-12-02 14:13:11 Re: [BUG] lo_open() makes a warning/falls to an assertion
Previous Message Alvaro Herrera 2008-12-02 14:03:48 Re: [BUG] lo_open() makes a warning/falls to an assertion

Browse pgsql-patches by date

  From Date Subject
Next Message Robert Haas 2008-12-02 22:52:07 Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1
Previous Message Teodor Sigaev 2008-12-02 12:56:33 Re: [PATCHES] GIN improvements