Message-ID: <485801AA.1000105@sigaev.ru>
Date: Tue, 17 Jun 2008 22:25:46 +0400
From: Teodor Sigaev <teodor@sigaev.ru>
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: Patches <pgsql-patches@postgresql.org>
Subject: Re: GIN improvements
References: <483FD205.4090904@sigaev.ru>
In-Reply-To: <483FD205.4090904@sigaev.ru>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit


> 1) multicolumn GIN
> Unlike other indexes, the performance of search 
> doesn't depends on what column of index (first, last, any subset) is 
> used in search clause. This property can be used in gincostestimate, but 
> I haven't looked on it yet.

After some playing I didn't find any mentions in *costestimate function about 
difference of cost estimation between first and any other columns in clauses, 
so, IMHO, issue above isn't an issue. :)

So, I didn't see any comments/objections and I intend to commit this patch for 
next two days and synchronize 'fast insert into GIN' patch with CVS.

Objections?

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/