unexpected result from to_tsvector - Mailing list pgsql-hackers

Hello,

Here is a little patch. It fixes this issue
http://www.postgresql.org/message-id/[email protected]

Without patch we get wrong result for the second email '[email protected]':

=> SELECT * FROM ts_debug('simple', '[email protected]');
  alias |  description  |       token        | dictionaries | dictionary
|       lexemes
-------+---------------+--------------------+--------------+------------+----------------------
  email | Email address | [email protected] | {simple}     | simple  |
{[email protected]}
(1 row)

=> SELECT * FROM ts_debug('simple', '[email protected]');
    alias   |   description    | token  | dictionaries | dictionary |
lexemes
-----------+------------------+--------+--------------+------------+----------
  asciiword | Word, all ASCII  | test   | {simple}     | simple     | {test}
  blank     | Space symbols    | @      | {}           |            |
  uint      | Unsigned integer | 123    | {simple}     | simple     | {123}
  blank     | Space symbols    | -      | {}           |            |
  host      | Host             | reg.ro | {simple}     | simple     |
{reg.ro}
(5 rows)

After patch we get correct result for the second email:

=> SELECT * FROM ts_debug('simple', '[email protected]');
  alias |  description  |      token      | dictionaries | dictionary |
       lexemes
-------+---------------+-----------------+--------------+------------+----------------------
  email | Email address | [email protected] | {simple}     | simple  |
{[email protected]}
(1 row)

This patch allows to parser work with emails '[email protected]',
'[email protected]' and 'test@123_reg.ro' correctly.

--
Artur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company