BUG #16168: Full text search parser prefers "file" over "asciiword"

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: chris(at)aha(dot)io
Subject: BUG #16168: Full text search parser prefers "file" over "asciiword"
Date: 2019-12-16 18:22:33
Message-ID: 16168-dbe201d295658f01@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16168
Logged by: Chris Waters
Email address: chris(at)aha(dot)io
PostgreSQL version: 10.5
Operating system: Any

When parsing an English string to form a term vector the parser will treat
any words separated by / as a file path. This is a problem when / is used in
normal English, e.g.

select to_tsvector('morning/afternoon');

I think it would be better if the parser output both the "file" and
"asciiword" versions of this string and indexed both.

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Lakhin 2019-12-16 19:00:00 Re: BUG #16162: create index using gist_trgm_ops leads to panic
Previous Message Jens.Wilke 2019-12-16 18:00:26 Missing locales prevent autovacuum