public inbox for [email protected]
help / color / mirror / Atom feedFrom: Oleg Bartunov <[email protected]>
To: Andreas Joseph Krogh <[email protected]>
To: Teodor Sigaev <[email protected]>
Cc: [email protected]
Subject: Re: Searching GIN-index (FTS) and sort by timestamp-column
Date: Mon, 21 Mar 2016 18:13:07 +0300
Message-ID: <CAF4Au4yV7tCuvLwJ=YoNVoToLYGn7RPz3h9vegHRpKUzh2+iZA@mail.gmail.com> (raw)
In-Reply-To: <VisenaEmail.3.72ca8808c48140d5.153999d91d6@tc7-visena>
References: <CAMkU=1zAcFQAdysVY6fyyR0k5OTgWvoja2TpkGBhe5t0E9RopA@mail.gmail.com>
<VisenaEmail.3.72ca8808c48140d5.153999d91d6@tc7-visena>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-performance>
On Mon, Mar 21, 2016 at 5:41 PM, Andreas Joseph Krogh <[email protected]>
wrote:
> På lørdag 19. mars 2016 kl. 03:44:55, skrev Jeff Janes <
> [email protected]>:
>
> On Wed, Mar 16, 2016 at 6:53 AM, Andreas Joseph Krogh <[email protected]>
> wrote:
>>
>> På onsdag 16. mars 2016 kl. 14:37:27, skrev Tom Lane <[email protected]>:
>>
>> Andreas Joseph Krogh <[email protected]> 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.
>
>
> Isn't this what Postgres Pro are planning?
> http://postgrespro.com/roadmap/mssearch
>
> *"Unlike external special-purpose search engines, a full-text search
> engine built in a DBMS is capable of combining full-text and attributive
> search criteria in SQL query syntax. It is planned to improve the existing
> PostgreSQL full-text search engine by extending the functionality of
> Generalized Inverted Index (GIN) to make it capable of storing extra
> information required for ranging query results. This search acceleration
> will allow to go back from external full-text search engines, thus
> facilitating system administration and use, reducing technology risks, and
> improving information security."*
>
This is different feature ! Actually, we already have prototype of what
Jeff suggested, we called it bitmap filtering, but failed to find use case
where it provides benefits. Teodor will comment this idea more detail.
>
> --
> *Andreas Joseph Krogh*
> CTO / Partner - Visena AS
> Mobile: +47 909 56 963
> [email protected]
> www.visena.com
> <https://www.visena.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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Searching GIN-index (FTS) and sort by timestamp-column
In-Reply-To: <CAF4Au4yV7tCuvLwJ=YoNVoToLYGn7RPz3h9vegHRpKUzh2+iZA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox