Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdZlu-0005VW-95 for pgsql-performance@arkaria.postgresql.org; Fri, 25 Apr 2014 06:38:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WdZlt-0005hX-Ky for pgsql-performance@arkaria.postgresql.org; Fri, 25 Apr 2014 06:38:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdZls-0005hQ-GZ for pgsql-performance@postgresql.org; Fri, 25 Apr 2014 06:38:04 +0000 Received: from smtp-outbound-2.vmware.com ([208.91.2.13]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdZlk-0003hQ-CY for pgsql-performance@postgresql.org; Fri, 25 Apr 2014 06:38:04 +0000 Received: from sc9-mailhost1.vmware.com (sc9-mailhost1.vmware.com [10.113.161.71]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id CFF9328844; Thu, 24 Apr 2014 23:37:54 -0700 (PDT) Received: from zcs-prod-ext-mta-1.vmware.com (zcs-prod-ext-mta-1.vmware.com [10.113.62.223]) by sc9-mailhost1.vmware.com (Postfix) with ESMTP id C7BC71910D; Thu, 24 Apr 2014 23:37:54 -0700 (PDT) Received: from zcs-prod-ext-mta-1.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-ext-mta-1.vmware.com (Postfix) with ESMTP id 50A8712002A; Thu, 24 Apr 2014 23:37:55 -0700 (PDT) Received: from [192.168.1.90] (zimbra-prod-ext-proxy-vip.vmware.com [10.113.63.87]) by zcs-prod-ext-mta-1.vmware.com (Postfix) with ESMTPSA; Thu, 24 Apr 2014 23:37:54 -0700 (PDT) Message-ID: <535A02C0.8060504@vmware.com> Date: Fri, 25 Apr 2014 09:37:52 +0300 From: Heikki Linnakangas Organization: VMware User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0 MIME-Version: 1.0 To: Sergey Konoplev , Ivan Voras CC: Jeff Janes , postgres performance list Subject: Re: tsearch2, large data and indexes References: <53560EE5.3080300@vmware.com> <5358F6BE.2020104@vmware.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -7.6 (-------) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 04/24/2014 10:57 PM, Sergey Konoplev wrote: > On Thu, Apr 24, 2014 at 5:34 AM, Ivan Voras wrote: >> On 24 April 2014 13:34, Heikki Linnakangas wrote: >> >>> As the docs say, the GIN index does not store the weights. As such, there is >>> no need to strip them. A recheck would be necessary if your query needs the >>> weights, precisely because the weights are not included in the index. >>> >>> (In the OP's query, it's the ranking that was causing the detoasting.) >> >> Thanks! >> >> My problem is that I actually need the ranking. My queries can return >> a large number of documents (tens of thousands) but I usually need >> only the first couple of pages of most relevant results (e.g. 50-100 >> records). With PostgreSQL and tsearch2, this means that the tens of >> thousands of documents found via the index are then detoasted and >> ranked. > > Heikki, what about the "GIN improvements part 3: ordering in index" > patch, was it committed? > > http://www.postgresql.org/message-id/flat/CAPpHfduWvqv5b0XZ1DZuqAW29erDCULZp2wotfJzDBs7BHpKXw@mail.gmail.com Nope, wasn't committed. - Heikki -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance