Question about RUM's TODO-list

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Question about RUM's TODO-list
Date: 2016-11-15 07:17:06
Message-ID: VisenaEmail.59.fb659a079e604d8c.15866cb6aac@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi.
 
The following TODO-items are on RUM's TODO-list:
 

* Allow multiple additional information (lexemes positions + timestamp).
* Add support for arrays.
 
Will any of these items support storing BIGINT as part of a tsvector+timestamp?
so one an have an index like this:
create index rum_idx on message using rum (fts_all some_opclass, folder_id,
received_timestamp)WITH (attach=received_timestamp, "to"=fts_all,
order_by_attach=t);
 
Making it possible for a query like this to use one index:
WHERE fts_all @@ to_tsquery('simple', 'andre:*&jose:*') AND folder_id = ANY(
ARRAY[2,3]::BIGINT[]) ORDER BY received_timestamp DESC LIMIT 10;
 
Thanks.
 
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Joseph Krogh 2016-11-15 07:37:08 Incorrect information about GIN-index in RUM's docs
Previous Message Mark Anns 2016-11-15 05:43:10 Re: How the Planner in PGStrom differs from PostgreSQL?