BUG #17043: Full text search - to_tsvector treating a full stop wrong

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: james(dot)inform(at)pharmapp(dot)de
Subject: BUG #17043: Full text search - to_tsvector treating a full stop wrong
Date: 2021-06-02 10:04:59
Message-ID: 17043-03f93dfe629bcc1b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17043
Logged by: James Inform
Email address: james(dot)inform(at)pharmapp(dot)de
PostgreSQL version: 13.3
Operating system: Mac and Ubuntu
Description:

It seems that to_tsvector is treating full stops wrong. If a sentence end
with a '.' and the following word isn't separated by a space, to_tsvector
will identify it as one lexeme:

select to_tsvector('english','This is the rat.Fat is she!')
'rat.fat':4

select to_tsvector('english','This is the rat. Fat is she!')
'fat':5 'rat':4

select to_tsvector('english','This is the rat.Fat is she!') @@
websearch_to_tsquery('fat')
false

select to_tsvector('english','This is the rat. Fat is she!') @@
websearch_to_tsquery('fat')
true

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-06-02 18:50:24 BUG #17044: installation of postgresql from the pgdg repository conflicts with Fedora's python gdal
Previous Message Kim-Alexander Brodowski 2021-06-01 22:06:59 Re: BUG #17042: Concurrent Modifications of PostgreSQL Function Can Corrupt Database