Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 4743B2E0064 for ; Tue, 10 Jun 2008 08:38:44 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 28870-07 for ; Tue, 10 Jun 2008 08:38:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from hook.sigaev.ru (hook.sigaev.ru [212.192.243.50]) by developer.postgresql.org (Postfix) with ESMTP id AA9D72E0056 for ; Tue, 10 Jun 2008 08:38:40 -0300 (ADT) Received: by hook.sigaev.ru (Postfix, from userid 1003) id 413CE39908; Tue, 10 Jun 2008 15:38:33 +0400 (MSD) Received: from xor.sai.msu.ru (ppp83-237-62-67.pppoe.mtu-net.ru [83.237.62.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hook.sigaev.ru (Postfix) with ESMTP id 6E719398E2; Tue, 10 Jun 2008 15:38:25 +0400 (MSD) Message-ID: <484E67AD.7020500@sigaev.ru> Date: Tue, 10 Jun 2008 15:38:21 +0400 From: Teodor Sigaev User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.13) Gecko/20080401 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Alvaro Herrera CC: Patches Subject: Re: GIN improvements References: <483FD205.4090904@sigaev.ru> <4849418C.6080909@sigaev.ru> <20080608224649.GC11028@alvh.no-ip.org> In-Reply-To: <20080608224649.GC11028@alvh.no-ip.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/67 X-Sequence-Number: 6553 > Right now this is not a problem because there is no insert_cleanup > function for btree, but I wonder if we should clean it up. Look at gistbulkdelete and gistvacuumcleanup, first function wants to send a bool flag to second one and they use GiSTBulkDelete structure instead of usual IndexBulkDeleteResult. When it will be needed btree may use the same method. > > FWIW there's a typo in catalogs.sgml (finction -> function) Thank you, will fix. > What's the use of the FASTUPDATE parameter? Is there a case when a user > is interested in turning it off? Yeah - when time of search is much-much more important (or crucial) than insertion time. Or table stores read-only values. -- Teodor Sigaev E-mail: teodor@sigaev.ru WWW: http://www.sigaev.ru/