From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: chris@aha.io
Subject: BUG #16168: Full text search parser prefers "file" over "asciiword"
Date: Mon, 16 Dec 2019 18:22:33 +0000
Message-ID: <16168-dbe201d295658f01@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16168
Logged by: Chris Waters
Email address: chris@aha.io
PostgreSQL version: 10.5
Operating system: Any
Description:
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');
to_tsvector
-----------------------
'morning/afternoon':1
I think it would be better if the parser output both the "file" and
"asciiword" versions of this string and indexed both.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, chris@aha.io
Subject: Re: BUG #16168: Full text search parser prefers "file" over "asciiword"
In-Reply-To: <16168-dbe201d295658f01@postgresql.org>
References: <16168-dbe201d295658f01@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox