Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1q9tRz-0005r3-1Q
	for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Jun 2023 20:20:11 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1q9tRx-0004Ba-TD
	for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Jun 2023 20:20:09 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1q9tRx-000491-Kf
	for pgsql-bugs@lists.postgresql.org; Thu, 15 Jun 2023 20:20:09 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1q9tRv-002PJI-9Y
	for pgsql-bugs@lists.postgresql.org; Thu, 15 Jun 2023 20:20:08 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 35FKK5bP2271904;
	Thu, 15 Jun 2023 16:20:06 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: vicreal@yandex.ru
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17979: (pg_tsparser + ts_headline) duplicate output if dot
 present
In-reply-to: <17979-ae3ed1932587b35c@postgresql.org>
References: <17979-ae3ed1932587b35c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 15 Jun 2023 16:40:03 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2271902.1686860405.1@sss.pgh.pa.us>
Date: Thu, 15 Jun 2023 16:20:05 -0400
Message-ID: <2271903.1686860405@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/2271903.1686860405%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> CREATE EXTENSION pg_tsparser;
> CREATE TEXT SEARCH CONFIGURATION public.vp_ts_config_test (PARSER =
> tsparser);
> SELECT ts_headline('vp_ts_config_test', 'one.two',
> websearch_to_tsquery('three'), 'HighlightAll=TRUE, StartSel="<mark>",
> StopSel="</mark>"');

> Result:
> one.twoone.two

I don't see any such misbehavior with the built-in parser,
so I think you need to report this to the author(s) of the
pg_tsparser extension.  This list is just concerned with
bugs in the core Postgres distribution.

			regards, tom lane