Re: Bug Report | Using ts_headline with the <-> operator

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: christian(at)games(dot)no
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Bug Report | Using ts_headline with the <-> operator
Date: 2021-01-20 15:38:53
Message-ID: 595533.1611157133@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

<christian(at)games(dot)no> writes:
> Assuming the following query:

> SELECT ts_headline('simple','The Cyberpunk launch did not go as expected for
> Cyberpunk Fans around the world', phraseto_tsquery('simple','Cyberpunk
> Fans')::tsquery);

> The returned result is:

> The <b>Cyberpunk</b> launch did not go as expected for <b>Cyberpunk</b>
> <b>Fans</b> around the world

This is behaving as designed, and I don't really think it's wrong.
See previous discussion at

https://www.postgresql.org/message-id/flat/16744-861496b4f8f941f2%40postgresql.org

It is unfortunate that the only way to customize this type of decision
is to build your own new text search parser. Perhaps someday someone
will put in the work to make that stuff a bit more modular and easier
to change.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-01-20 21:04:56 BUG #16831: Idle postgres processes on Linux consumes huge amount of memory
Previous Message Tom Lane 2021-01-20 15:25:10 Re: Reproducible GIST index corruption under concurrent updates