Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7F78B6503E0 for ; Wed, 3 Dec 2008 10:36:18 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 10531-03 for ; Wed, 3 Dec 2008 10:36:16 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 0194D65033B for ; Wed, 3 Dec 2008 10:36:06 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id mB3EZXSN007856; Wed, 3 Dec 2008 09:35:33 -0500 (EST) To: Greg Stark cc: Heikki Linnakangas , Teodor Sigaev , Pgsql Hackers Subject: Re: [PATCHES] GIN improvements In-reply-to: <683CE0EA-799C-4644-9C9F-74AECD2BFBDC@enterprisedb.com> References: <483FD205.4090904@sigaev.ru> <486BC501.6060605@sigaev.ru> <27880.1215810535@sss.pgh.pa.us> <487A6E0C.3090600@sigaev.ru> <8993.1216843701@sss.pgh.pa.us> <4888A594.6010102@sigaev.ru> <490B07BA.6030109@sigaev.ru> <492F04D9.5070404@enterprisedb.com> <49353081.9030304@sigaev.ru> <493541F5.2020401@enterprisedb.com> <26721.1228266365@sss.pgh.pa.us> <49362DF0.80404@enterprisedb.com> <683CE0EA-799C-4644-9C9F-74AECD2BFBDC@enterprisedb.com> Comments: In-reply-to Greg Stark message dated "Wed, 03 Dec 2008 09:40:07 +0000" Date: Wed, 03 Dec 2008 09:35:33 -0500 Message-ID: <7855.1228314933@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/156 X-Sequence-Number: 128785 Greg Stark writes: > If we do this though it would be really nice to do it at a higher > level than the indexam. If we could do it for any indexam that > provides a kind of bulk insert method that would be great. > I'm just not sure how to support all the indexable operators for the > various indexams on the local buffered list. In principle, just return all those TIDs marked "lossy, please recheck". This is a bit brute-force but I'm not sure any useful optimization is possible. regards, tom lane