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 ) id 1wDkQk-003JLS-0c for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Apr 2026 14:44:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wDkQj-00AQbc-0q for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Apr 2026 14:44:25 +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 ) id 1wDkQi-00AQWq-2s for pgsql-hackers@lists.postgresql.org; Fri, 17 Apr 2026 14:44:24 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wDkQg-00000001UHb-35Is for pgsql-hackers@lists.postgresql.org; Fri, 17 Apr 2026 14:44:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=a5b0OLaCzpA8smhitIvzhdcitet3XFMPgptghbInFWY=; b=tsoyp SA+J3jsKnmqXY6oZaGzhBFBTraYZpJ/ubUBL+ZF9NIzd7Sarfc3ouMN1Hq4DTatjMbXIKlT1XDobK bc6zRJKICL0CovJdQKNyCn/1MFAvMfTyq9fPgBZNXHy/q6URDHMRmR/x8IAiR6ITHji+dka60veNv u0gHQiTprlfqabJk2F7rOdht8SKv+Dn6QIVQ5mf42eIMFJPT0z3vUuuoKoI1/SNIs6DSvwJcM8jbf EAaoJTOjXqRuif1qVEpFsOGvMGoYBEr3nqnDNBcvtJ7yf8QR2fuc/VR3/DM1MJBifKAh64QJOoaX+ mHdeGjkJz+7vx70w0KYnsA62BBdIw==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wDkQg-0000000AECv-0oi9; Fri, 17 Apr 2026 10:44:22 -0400 Date: Fri, 17 Apr 2026 10:44:22 -0400 From: Bruce Momjian To: David Geier Cc: PostgreSQL-development Subject: Re: First draft of PG 19 release notes Message-ID: References: <5d58c42f-11e2-432c-a926-49d16d890c99@gmail.com> <79bc2b67-b0c1-4945-a5df-1b4f71d32a48@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79bc2b67-b0c1-4945-a5df-1b4f71d32a48@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Apr 17, 2026 at 04:40:09PM +0200, David Geier wrote: > > Now that you have told me about it, here is my normal criteria for > > adding performance items to the release notes: > > > > Performance improvements are mentioned in the release notes if > > they are user-visible (e.g., new syntax) or significant enough > > to enable new workloads. > > > > So, it seems there is no user-visible change, except it is faster. Does > > it enable new workloads? A 3x speedup probably does. Should this be a > > pg_trgm item, with a description mentioning GIN in general, or should it > > be a GIN item, perhaps mentioning pg_trgm? Do you have any suggested > > text and list of commits? > > Not all patches from the initial mail have been committed yet. Hence, > currently the speed up is less. However, once they got all committed > they would indeed open up new "use cases". For example, I know users > that don't add GIN indexes to very large tables because creating them > takes too long. Yes, GIN index creation has always been considered slow, so it is good it is being worked on. I wonder if we should just wait for it all to be committed before adding it to the release notes, unless you want to measure the improvement we have in PG 19. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.