Re: Searching for pgweb

On Wed, Mar 22, 2017 at 7:51 PM, Magnus Hagander <magnus@hagander.net> wrote:

Right now our main website search uses plainto_tsquery() to generate the searches.

Should we consider switching that to phraseto_tsquery() now that we have phrase searching?

+1

Also, I suggest to use new parser, which better works _ and -, for example:

1.  
select ts_parse('tsparser', 'btree_gin');
    ts_parse
----------------
 (16,btree_gin)
 (11,btree)
 (12,_)
 (11,gin)
(4 rows)

select ts_parse('default', 'btree_gin');
 ts_parse
-----------
 (1,btree)
 (12,_)
 (1,gin)
(3 rows)

Default parser produces too much noise, just check the difference:

https://postgrespro.ru/search/?area=version&q=btree_gin&product=postgresql&version=9.6

https://www.postgresql.org/search/?u=%2Fdocs%2F9.6%2F&q=btree_gin

 
2. 
select ts_parse('tsparser', 'utc-5');
  ts_parse
------------
 (15,utc-5)
 (11,utc)
 (12,-)
 (9,5)
(4 rows)

select ts_parse('default', 'utc-5');
 ts_parse
----------
 (1,utc)
 (21,-5)
(2 rows)

again, compare

https://postgrespro.ru/search/?area=version&q=utc-5&product=postgresql&version=9.6

https://www.postgresql.org/search/?u=%2Fdocs%2F9.6%2F&q=utc-5

We have also better parsing of email, but I'm not sure we need it on postgres site.

We'll publish soon on github, let me know if you know it.