Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1wqcX7-002JjN-2L
	for pgsql-bugs@arkaria.postgresql.org;
	Sun, 02 Aug 2026 20:11:41 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1wqcX6-003Hng-0L
	for pgsql-bugs@arkaria.postgresql.org;
	Sun, 02 Aug 2026 20:11:40 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1wqcX5-003HnY-2m
	for pgsql-bugs@lists.postgresql.org;
	Sun, 02 Aug 2026 20:11:39 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.98.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1wqcX4-00000001avo-0f6I
	for pgsql-bugs@lists.postgresql.org;
	Sun, 02 Aug 2026 20:11:39 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 672KBYjM336528;
	Sun, 2 Aug 2026 16:11:34 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lakhin <exclusion@gmail.com>
cc: Andrey Rachitskiy <pl0h0yp1@gmail.com>, michaelmalis2@gmail.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19595: Three memory-safety defects in
 src/backend/tsearch/spell.c (dictionary loader), PG 18.3
In-reply-to: <0f3ddeb5-0dbd-479c-9d0e-ae254758e624@gmail.com>
References: <19595-7dc18b4e212c4757@postgresql.org>
 <CAB8bMiun+cTqTnv-cTfxvTbnOLxWunRgyZeUZ88YMSLLXub4mg@mail.gmail.com>
 <325748.1785691547@sss.pgh.pa.us>
 <0f3ddeb5-0dbd-479c-9d0e-ae254758e624@gmail.com>
Comments: In-reply-to Alexander Lakhin <exclusion@gmail.com>
	message dated "Sun, 02 Aug 2026 23:00:01 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <336526.1785701494.1@sss.pgh.pa.us>
Date: Sun, 02 Aug 2026 16:11:34 -0400
Message-ID: <336527.1785701494@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/336527.1785701494%40sss.pgh.pa.us>
Precedence: bulk

Alexander Lakhin <exclusion@gmail.com> writes:
> I'm not sure it's directly related to this bug report, but maybe you'd
> like to fix one more memory-safety defect in tsearch in passing...

Hmph.  Not sure I'd call that "memory safety", but yeah, this bit
isn't being careful about having a valid intermediate state of the
data structure.  Thanks for the report!

			regards, tom lane