Skip site navigation (1) Skip section navigation (2)

GIN fast insert

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: GIN fast insert
Date: 2009-02-17 19:28:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Hi there,

we present two variants of GIN fast insert patch, since we're not sure
what is a the best solution:

- remove disable cost in gincostestimate
- per
   gingettuple could force cleanup of pending list if it got a lossy tidbitmap.
   If such cleanup occurs the gingettuple will rescan pending list again.

- remove disable cost in gincostestimate
- per
   AM can now have only one search method: amgettuple or amgetbitmap.
- GIN now has only amgetbitmap interface
Teodor Sigaev                                   E-mail: teodor(at)sigaev(dot)ru

Attachment: fast_insert_gin-0.28.1.gz
Description: application/x-tar (24.1 KB)
Attachment: fast_insert_gin-0.28.2.gz
Description: application/x-tar (25.1 KB)


pgsql-hackers by date

Next:From: Brendan JurdDate: 2009-02-17 19:36:52
Subject: Re: Questions about parsing boolean and casting to anyelement
Previous:From: Brendan JurdDate: 2009-02-17 19:24:28
Subject: Re: [BUGS] BUG #4660: float functions return -0

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group