Re: tsearch parser inefficiency if text includes urls or emails - new version
От
Kevin Grittner
Тема
Re: tsearch parser inefficiency if text includes
urls or emails - new version
Дата
Msg-id
4B20F209020000250002D317@gw.wicourts.gov
Ответ на
Список
Дерево обсуждения
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes urls or emails - new version Andres Freund <andres@anarazel.de>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes urls or emails - new version Andres Freund <andres@anarazel.de>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes urls
or emails - new version Greg Smith <greg@2ndquadrant.com>
Re: tsearch parser inefficiency if text includes urls or emails - new version Andres Freund <andres@anarazel.de>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes urls
or emails - new version Greg Smith <greg@2ndquadrant.com>
Re: tsearch parser inefficiency if text includes urls or emails - new version Tom Lane <tgl@sss.pgh.pa.us>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes urls or
emails - new version Greg Smith <greg@2ndquadrant.com>
Re: tsearch parser inefficiency if text includes urls or emails - new version Andres Freund <andres@anarazel.de>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes urls or emails - new version Andres Freund <andres@anarazel.de>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes urls or emails - new version Tom Lane <tgl@sss.pgh.pa.us>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: tsearch parser inefficiency if text includes
urls or emails - new version "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
I wrote: > I did find one significant (although easily solved) problem. In > the patch, the recursive setup of usewide, pgwstr, and wstr are > not conditioned by #ifdef USE_WIDE_UPPER_LOWER in the non-patched > version. Unless there's a good reason for that, the #ifdef should > be added. That should read: I did find one significant (although easily solved) problem. In the patch, the recursive setup of usewide, pgwstr, and wstr are not conditioned by #ifdef USE_WIDE_UPPER_LOWER as they are in the non-patched version. Unless there's a good reason for that, the #ifdef should be added. -Kevin
В списке pgsql-hackers по дате отправления
От: Andres Freund
Дата: