BUG #15488: Unexpected behaviour of to_tsverctor and ts_query

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: nikolajs(dot)arhipovs(at)gmail(dot)com
Subject: BUG #15488: Unexpected behaviour of to_tsverctor and ts_query
Date: 2018-11-06 12:51:58
Message-ID: 15488-a738bcc48f1af087@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: 15488
Logged by: Nikolajs Arhipovs
Email address: nikolajs(dot)arhipovs(at)gmail(dot)com
PostgreSQL version: 9.6.8
Operating system: Linux, kernel 4.18.16-arch1-1-ARCH
Description:

I am trying to do prefix search of emails using full text search. Emails
sometimes contain dot symbols.
Now, select to_tsquery('simple', 'thing.a:*'); returns a single term as
expected but
select to_tsquery('simple', 'the.thing.a:*') suddenly tokenizes my search
expression into 'the.thing':* & 'a':*. At the same time select
to_tsquery('simple', 'the.thing.aa:*'); tokenizes as expected into a single
term.
Also select to_tsquery('simple', 'the(dot)thing(at)gmail(dot)com'); returns a single
term as expected, but select to_tsquery('simple', 'the(dot)thing(at)gma:*'); splits
on @ char and returns two tokens.
This behavior is not covered in the official documentation.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2018-11-06 15:10:13 Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
Previous Message Etsuro Fujita 2018-11-06 12:07:37 Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT