Re: Phrase search vs. multi-lexeme tokens - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Phrase search vs. multi-lexeme tokens
Date
Msg-id CAPpHfdu5kGfV3Mi_uqHwnyGjfzj4kRM+GF_5bmVwDsW05KKypA@mail.gmail.com
Whole thread Raw
In response to Phrase search vs. multi-lexeme tokens  (Alexander Korotkov <aekorotkov@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Improving spin-lock implementation on ARM.
Next
From: Heikki Linnakangas
Date:
Subject: Re: Avoid using lcons and list_delete_first in plan_union_children()