Artur Zakirov

We find a solution. We can add new OPERATOR CLASS which will store hash of lexems, then you can store huge strings. But in this OPERATOR CLASS we cant use...

> Can you trim the url and raise some notice like: > > NOTICE: Index key can't have size more than 1336 bytes. > HINT: key has been trimmed. I...

@To4e , please can you check the **issue_9_max_item_size** branch? https://github.com/postgrespro/rum/tree/issue_9_max_item_size

Hello, Can you describe your task more detailed? Do you mean inherited tables or **partitions**? Do you mean creation of indexes for each table or creation of one global index...

Unfortunately currently it isn't possible to create a global index. It is an issue not only of RUM, but also of PostgreSQL itself. > "But it recursively creates indexes for...

I'm not sure that I understood you correctly. Can you give an example of queries and tables?

I think you can use `UNION` statement here. And also you can use here a view (not materialized) as Oleg wrote. Does this work for you?

> the generation of the rum index with the presence of children's tables, to do it in a loop on each table, then the index will be complete and consistent,...

Yes. Let's say we have two tables: ``` =# \d+ test_rum Column | Type --------+---------- t | text a | tsvector Indexes: "rumidx" rum (a) Child tables: test_rum_2 =# \d+...

Hello @ngigiwaithaka , Thank you for the issue! Unfortunately it isn't possible to attach exression's result as a additional information nowadays. `attach` and `to` options in `WITH` expression requires column...