| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Phrase search vs. multi-lexeme tokens |
| Date: | 2020-12-01 16:13:53 |
| Message-ID: | CAPpHfdu5kGfV3Mi_uqHwnyGjfzj4kRM+GF_5bmVwDsW05KKypA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 12, 2020 at 4:09 PM Alexander Korotkov <aekorotkov(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2020-12-01 16:17:24 | Re: Avoid using lcons and list_delete_first in plan_union_children() |
| Previous Message | Alexander Korotkov | 2020-12-01 16:07:02 | Re: Improving spin-lock implementation on ARM. |