Re: Rethinking the implementation of ts_headline()

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, sebastian(dot)patino-lang(at)posteo(dot)net
Subject: Re: Rethinking the implementation of ts_headline()
Date: 2023-01-17 08:32:11
Message-ID: 20230117083211.ogkkfwjij42qfyoc@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-Jan-16, Tom Lane wrote:

> I get this with the patch:
>
> ts_headline | ts_headline
> ---------------------+---------------------
> {ipsum} ... {labor} | {ipsum} ... {labor}
> (1 row)
>
> which is what I'd expect, because it removes the artificial limit on
> cover length that I added in 78e73e875. So I'm wondering why you got a
> different result.

Indeed, that's what I get now, too, after re-applying the patches.
I find no way to reproduce the bogus result I got yesterday.

Sorry for the noise.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Every machine is a smoke machine if you operate it wrong enough."
https://twitter.com/libseybieda/status/1541673325781196801

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-01-17 09:11:00 Re: Exit walsender before confirming remote flush in logical replication
Previous Message Laurenz Albe 2023-01-17 08:05:34 Re: The documentation for storage type 'plain' actually allows single byte header