Re: [HACKERS] Flexible configuration for full-text search

2017-11-29 Thread Michael Paquier
On Tue, Nov 7, 2017 at 3:18 PM, Aleksandr Parfenov wrote: > On Mon, 6 Nov 2017 18:05:23 +1300 > Thomas Munro wrote: > >> On Sat, Oct 21, 2017 at 1:39 AM, Aleksandr Parfenov >> wrote: >> > In attachment updated patch with fixes of empty XML tags in >> > documentation. >> >> Hi Aleksandr, >> >> I'

Re: [HACKERS] Flexible configuration for full-text search

2017-12-21 Thread Arthur Zakirov
Hello, On Tue, Dec 19, 2017 at 05:31:09PM +0300, Aleksandr Parfenov wrote: > > The new version of the patch is in attachment as well as a > little README file with a description of changes in each file. Any > feedback is welcome. > I looked the patch a little bit. The patch is applied and tests

Re: [HACKERS] Flexible configuration for full-text search

2017-12-25 Thread Aleksandr Parfenov
Hi Arthur, Thank you for the review. On Thu, 21 Dec 2017 17:46:42 +0300 Arthur Zakirov wrote: > I noticed that there are typos in the documentation. And I think it > is necessary to keep information about previous sintax. The syntax > will be supported anyway. For example, information about TSL

Re: [HACKERS] Flexible configuration for full-text search

2017-12-26 Thread Arthur Zakirov
On Mon, Dec 25, 2017 at 05:15:07PM +0300, Aleksandr Parfenov wrote: > > In the current version of the patch, configurations written in old > syntax are rewritten into the same configuration in the new syntax. > Since new syntax doesn't support a TSL_FILTER, it was removed from the > documentation.

Re: [HACKERS] Flexible configuration for full-text search

2017-12-26 Thread Aleksandr Parfenov
On Tue, 26 Dec 2017 13:51:03 +0300 Arthur Zakirov wrote: > On Mon, Dec 25, 2017 at 05:15:07PM +0300, Aleksandr Parfenov wrote: > > Is I understood users need to rewrite their configurations if they > use unaccent dictionary, for example. It is not good I think. Users > will be upset about that i