From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Searching GIN-index (FTS) and sort by timestamp-column |
Date: | 2016-03-19 02:44:55 |
Message-ID: | CAMkU=1zAcFQAdysVY6fyyR0k5OTgWvoja2TpkGBhe5t0E9RopA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Mar 16, 2016 at 6:53 AM, Andreas Joseph Krogh <andreas(at)visena(dot)com>
wrote:
> På onsdag 16. mars 2016 kl. 14:37:27, skrev Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Andreas Joseph Krogh <andreas(at)visena(dot)com> writes:
> > 1. Why isnt' folder_id part of the index-cond?
>
> Because a GIN index is useless for sorting.
>
> > 2. Is there a way to make it use the (same) index to sort by
> > received_timestamp?
>
> No.
>
> > 3. Using a GIN-index, is there a way to use the index at all for sorting?
>
> No.
>
> > 4. It doesn't seem like ts_rank uses the index for sorting either.
>
> Same reason.
>
> regards, tom lane
>
>
> So it's basically impossible to use FTS/GIN with sorting on large datasets?
> Are there any plans to improve this situation?
>
I don't see why it would not be possible to create a new execution node
type that does an index scan to obtain order (or just to satisfy an
equality or range expression), and takes a bitmap (as produced by the
FTS/GIN) to apply as a filter. But, I don't know of anyone planning on
doing that.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Sofen | 2016-03-19 03:22:25 | Re: Disk Benchmarking Question |
Previous Message | Adrian Klaver | 2016-03-18 21:46:46 | Re: [GENERAL] grant select on pg_stat_activity |