Re: Phrase search vs. multi-lexeme tokens
Alexander Korotkov <aekorotkov@gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-12-01T16:13:53Z
Lists: pgsql-hackers
On Thu, Nov 12, 2020 at 4:09 PM Alexander Korotkov <aekorotkov@gmail.com> wrote: > This issue looks like the much more complex design bug in phrase > search. Fixing this would require some kind of readahead or multipass > processing, because we don't know how to process 'pg_class' in > advance. > > Is this really a design bug existing in phrase search from the > beginning. Or am I missing something? No feedback yet. I've added this to the commitfest to don't lose track of this. https://commitfest.postgresql.org/31/2854/ ------ Regards, Alexander Korotkov
Commits
-
Fix parsing of complex morphs to tsquery
- 0c4f355c6a5f 14.0 landed