Hi there,

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

v0.28.1
- remove disable cost in gincostestimate
- per http://archives.postgresql.org/message-id/499466D2(dot)4010808(at)sigaev(dot)ru
   gingettuple could force cleanup of pending list if it got a lossy tidbitmap.
   If such cleanup occurs the gingettuple will rescan pending list again.

v0.28.2
- remove disable cost in gincostestimate
- per http://archives.postgresql.org/message-id/12795(dot)1234379754(at)sss(dot)pgh(dot)pa(dot)us
   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
                                                    WWW: http://www.sigaev.ru/

Responses

• Re: GIN fast insert at 2009-02-19 03:57:31 from Robert Haas
• Re: GIN fast insert at 2009-03-23 19:19:20 from Tom Lane

pgsql-hackers by date

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