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.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1ta4WR-00Fs6P-Gu
	for pgsql-bugs@arkaria.postgresql.org; Tue, 21 Jan 2025 03:01:47 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1ta4WQ-00A9Qj-6n
	for pgsql-bugs@arkaria.postgresql.org; Tue, 21 Jan 2025 03:01:46 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.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 1ta4WP-00A9Qb-Uv
	for pgsql-bugs@lists.postgresql.org; Tue, 21 Jan 2025 03:01:45 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.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 1ta4WM-000dxY-1q
	for pgsql-bugs@lists.postgresql.org;
	Tue, 21 Jan 2025 03:01:45 +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 50L31eEq3265440;
	Mon, 20 Jan 2025 22:01:41 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "=?utf-8?B?6LCt5b+g5rab?=" <zhongtao.tan@seaboxdata.com>
cc: "=?utf-8?B?cGdzcWwtYnVncw==?=" <pgsql-bugs@lists.postgresql.org>
Subject: Re: Performance Issue when using gin index
In-reply-to: <tencent_7773A0055A04795D1E3DB6E3@qq.com>
References: <tencent_7773A0055A04795D1E3DB6E3@qq.com>
Comments: In-reply-to "=?utf-8?B?6LCt5b+g5rab?=" <zhongtao.tan@seaboxdata.com>
	message dated "Tue, 21 Jan 2025 10:30:24 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3265438.1737428500.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Jan 2025 22:01:40 -0500
Message-ID: <3265439.1737428500@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/3265439.1737428500%40sss.pgh.pa.us>
Precedence: bulk

"=3D?utf-8?B?6LCt5b+g5rab?=3D" <zhongtao.tan@seaboxdata.com> writes:
> The performance of creating a gin index before inserting data is differe=
nt from that of inserting data after creating a gin index.

This isn't terribly surprising.  Read

https://www.postgresql.org/docs/current/gin.html#GIN-FAST-UPDATE

There's also useful info in

https://www.postgresql.org/docs/current/gin.html#GIN-TIPS

			regards, tom lane