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 1wFHuh-004w7N-1x for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Apr 2026 20:41:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wFHuf-00APTx-2u for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Apr 2026 20:41:41 +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.96) (envelope-from ) id 1wFHuf-00APTp-20 for pgsql-hackers@lists.postgresql.org; Tue, 21 Apr 2026 20:41:41 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wFHud-00000002MMX-1SDm for pgsql-hackers@lists.postgresql.org; Tue, 21 Apr 2026 20:41:41 +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=OnziwozSmXz3P1rTT5I3V2LGepQjtreLdmiZAsYPvF8=; b=dHSsC pnsX5zR5QtMptGsScKmB9XFNOBbJX7mXg81rbPKqjRmdpWCK6lMmqrf7cFTSna5ruW1H+padPk4UP E0ODrwKYfbv3exwC5bA3RDeWDkZazADE1v6AG+c5wWfqNtuIU4h4rTgMxwt2CA15GHO/OLlkPGTqn +nt+a3CY3KVy3wGDeLZBGNrH0OelAlrY+lKkzOUbDVsLvoBlEB0vdWJpZIJrCCOvIGIJvDgt2Elvb dhtmk19XUAXJmP/GLRKZaXC7zURymazWT0zFXRU3tmAMAN8HmChRVDbXFmYxGglQnLGWYyn66W6ud UyAR0RpYOSv71ts/HeVMp87K+d3qQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wFHua-0000000CYvz-2b37; Tue, 21 Apr 2026 16:41:36 -0400 Date: Tue, 21 Apr 2026 16:41:36 -0400 From: Bruce Momjian To: Andres Freund Cc: David Rowley , David Geier , PostgreSQL-development Subject: Re: First draft of PG 19 release notes Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Apr 21, 2026 at 11:52:37AM -0400, Andres Freund wrote: > FWIW, I think it's totally fine if you say that you don't want to do the work > to formulate performance improvement release note entries. It's a lot of work > to curate the release notes, it makes sense to split the work up. > > It's just that the answer to proposing listing certain performance > improvements shouldn't be that we don't include them as a matter of policy. I am fine with listing anything, as long as it is effective and useful to the reader. I explained in my recent email why I considered that to be very hard for performance items, but with help I think it can be achieved. New optimizer items are a good example --- we reference plan types. I need help in how other items can have similar effectiveness. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.