Drawback of`RUM` is that it has slower build and insert time than`GIN`.

It is because we need to store additional information besides keys and because

`RUM` uses generic WAL.

`RUM` uses generic WAL records.

Supported operations:`<`,`<=`,`=`,`>=`,`>` for all types and

`<=>`,`<=|` and`|=>` for int2, int4, int8, float4, float8, money, oid,

timestamp and timestamptz types.

timestamp and timestamptz types.

Supports ordering by`<=>`,`<=|` and`|=>` operators. Can be used with

`rum_tsvector_addon_ops`,`rum_tsvector_hash_addon_ops' and`rum_anyarray_addon_ops` operator classes.

EXPLAIN (costs off)

SELECT id, d, d<=>'2016-05-16 14:21:25'FROM tstsWHERE t @@'wr&qh'ORDER BY d<=>'2016-05-16 14:21:25'LIMIT5;

QUERY PLAN

QUERY PLAN

-> Index Scan using tsts_idxon tsts

(4 rows)

SELECT id, d, d<=>'2016-05-16 14:21:25'FROM tstsWHERE t @@'wr&qh'ORDER BY d<=>'2016-05-16 14:21:25'LIMIT5;

id | d | ?column?

id | d | ?column?

355 | Mon May1614:21:22.3267242016 |2.673276

354 | Mon May1613:21:22.3267242016 |3602.673276

SELECT*FROM query

WHERE to_tsvector('black holes never exists before we think about them') @@ q;

q | tag

q | tag

'black' | color

'black' &'hole' | color