| From: | Johannes Graën <johannes(dot)graen(at)gmail(dot)com> |
|---|---|
| To: | hmidi slim <hmidi(dot)slim2(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Combine multiple text search configuration |
| Date: | 2017-11-09 08:09:49 |
| Message-ID: | c2114369-d741-0226-85d5-63ba1c651fb9@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2017-11-07 08:27, hmidi slim wrote:
> Hi,
> Thank for your proposition but when to use this query :
> (to_tsvector('english', document) || to_tsvector('french', document)) @@
> (to_tsquery('english', query) || to_tsquery('french', query))
> I think that the performance decrease and not a good solution for big
> amount of data. Is it?
You have more lexems when you combine two languages, but not twice as
many as there will be some overlap. That means your index will also be
be bigger than a single language index. Anyhow I would expect this
variant to perform better than querying two single columns
simultaneously. Maybe one of the FTS developers could comment on this?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johannes Graën | 2017-11-09 08:11:07 | Fwd: Re: Combine multiple text search configuration |
| Previous Message | Mayank Agrawal | 2017-11-09 07:54:38 | PostgreSQL 9.5 showing unexpected behavior when installed with different locale other than default |