Re: GIN fast insert

Teodor Sigaev wrote:
>> So?  Barring some evidence that there's a significant performance win
>> from a conventional indexscan, this is a weak argument.  AFAICS the only
>> significant advantage of the conventional API is to support ordered
>> scans, and GIN doesn't do that anyway.
> What about  SELECT ... AND EXISTS (SELECT ... t @@ query) ?
> But I don't believe that is popular use-case. In most cases, GIN is used 
> with bitmap scan. Your emails are so convincing and I'll remove support 
> amgettuple interface in GIN.

SELECT * FROM foo WHERE t @@ query LIMIT 100

might be a fairly common use case.

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