| From: | Artur Zakirov <zaartur(at)gmail(dot)com> |
|---|---|
| To: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
| Cc: | mnelson(at)binarykeep(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Text search prefix matching and stop words |
| Date: | 2021-10-11 14:50:51 |
| Message-ID: | CAKNkYnw63mGssUzeKb=FVPXwOXmV_Qrk0fd6pozHvFuDQD1Pfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 8, 2021 at 10:31 PM Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> wrote:
> If you want to process successive characters typing, you can use casting to tsvector type until input is not finished
>
> 'over:*'::tsquery;
Also it is possible to use a custom configuration without stop words
if you want normalization:
postgres=# select to_tsquery('english_wo_stop', 'over:*') &&
to_tsquery('english', 'foo');
?column?
------------------
'over':* & 'foo'
--
Artur
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-10-11 15:25:49 | BUG #17220: ALTER INDEX ALTER COLUMN SET (..) with an optionless opclass makes index and table unusable |
| Previous Message | Emil Iggland | 2021-10-11 14:07:40 | Re: BUG #17141: SELECT LIMIT WITH TIES FOR UPDATE SKIP LOCKED returns wrong number of rows |