pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Sergey Konoplev <gray.ru@gmail.com>
To: Ivan Voras <ivoras@freebsd.org>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: tsearch2, large data and indexes
Date: Fri, 25 Apr 2014 09:37:52 +0300
Message-ID: <535A02C0.8060504@vmware.com> (raw)
In-Reply-To: <CAL_0b1sREcX8jtf5O_e4Sd7kNrK3n04n1szPgtBhCdKSTnF46Q@mail.gmail.com>
References: <CAF-QHFUaRk-v4bnTUQ0_eepH0MEKaCaVM-fwiTP1uxM8EgKQVw@mail.gmail.com>
	<53560EE5.3080300@vmware.com>
	<CAF-QHFWbee3Anp+KKc5DEe2wufHtWYZ8zc1ysqXu2-0SW+v-UA@mail.gmail.com>
	<CAMkU=1y7-HOb2=iNkmPXC_mePRqSnkftCG5UdStrzwDJBO7WLg@mail.gmail.com>
	<CAF-QHFVYw5-2MwAVqCpZp8spyEfVP_k918naG=XV0ypTe=gOvA@mail.gmail.com>
	<CAL_0b1vo9ibxHG3MayGKNxiOJH3is3kav5E1x+eBQZv6QC4Wow@mail.gmail.com>
	<5358F6BE.2020104@vmware.com>
	<CAF-QHFWNt-+AKyYQDf=d56b198tRObmfrNwzBj78h2CLUw3T4g@mail.gmail.com>
	<CAL_0b1sREcX8jtf5O_e4Sd7kNrK3n04n1szPgtBhCdKSTnF46Q@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

On 04/24/2014 10:57 PM, Sergey Konoplev wrote:
> On Thu, Apr 24, 2014 at 5:34 AM, Ivan Voras <ivoras@freebsd.org> wrote:
>> On 24 April 2014 13:34, Heikki Linnakangas <hlinnakangas@vmware.com> 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.g...

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



view thread (13+ messages)

Message-ID: <535A02C0.8060504@vmware.com>
Permalink:  ../535A02C0.8060504@vmware.com/
Also on:    postgresql.org/message-id/535A02C0.8060504@vmware.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: hlinnakangas@vmware.com, gray.ru@gmail.com, ivoras@freebsd.org, jeff.janes@gmail.com
  Subject: Re: tsearch2, large data and indexes
  In-Reply-To: <535A02C0.8060504@vmware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox