From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alex Malek <magicagent(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, ngigi(at)at(dot)co(dot)ke |
Subject: | Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly |
Date: | 2023-10-28 23:39:56 |
Message-ID: | ZT2bzCEZ1UgpAe7a@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, Oct 29, 2023 at 01:20:11AM +0400, Pavel Borisov wrote:
> Hi, Bruce and Tom!
> I think that the ts_headline main functionality is to make Postgres
> more friendly to search-engine-like approach, which I feel is too
> niche usage scenario for supporting it as a part of core code. If
> remember right, bug reports coming from the users supposing it has
> more strict semantics than it has in reality are regular. And I also
> remember myself being puzzled by unusual output in the past.
>
> If we fiddle with other parameters of ts_headline we can easily have
> other kinds of output that seem counterintuitive e.g.:
> SELECT ts_headline('English',
I just posted a proposed doc patch which should help reduce the number
of people surprised by the highlighting. Let's see if that helps.
FYI, here is a Stack Overflow post from 2021 linking to the original
email that started this thread from 2018:
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-10-29 15:53:35 | Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly |
Previous Message | Bruce Momjian | 2023-10-28 23:34:42 | Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly |