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 1wEX0w-004759-0H for pgsql-hackers@arkaria.postgresql.org; Sun, 19 Apr 2026 18:37:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wEX0v-00FtbG-0R for pgsql-hackers@arkaria.postgresql.org; Sun, 19 Apr 2026 18:37:01 +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 1wEX0u-00Ftb7-2i for pgsql-hackers@lists.postgresql.org; Sun, 19 Apr 2026 18:37:00 +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 1wEX0s-00000001o53-2OCd for pgsql-hackers@lists.postgresql.org; Sun, 19 Apr 2026 18:36:59 +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=UwiA7Atv8Cec4UNYeOc2ixeigJVa3KAkrqL07pY31jw=; b=HLg0t peTHwB/vAnpBsN+MGiI38i9x89iClxR5/NUECNkGD4ik4YBPcEEoyfUtJ3zX+ZzfhgoG+wK/QchwG VuiE6Fh+F1QvfMvmEoYTL9DkIG9/tNmm3IfJHcgLCBSLpHByAJwX5QWfMxz/zp2OtkDyHuqj+H3iE HAtVwKNAFzZLVIaUae1ZpFeohsysFjrtUK2J+XF97e4ukGTVwjXsLWocnYxx2EGIIH1gswkPgPAeH 3L71G4VBgqTzo70lrWkGai6Gnv8BHr1T04XXnAO5KPtucpZ8a4CSua1eZ4NrNXQIpw2dAQ73r4lIm 1J+tufeJtESVDPBq61RmIWKDVBSRQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wEX0r-000000068Y8-46m5; Sun, 19 Apr 2026 14:36:57 -0400 Date: Sun, 19 Apr 2026 14:36:57 -0400 From: Bruce Momjian To: Andres Freund Cc: David Geier , 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> <3407474c-9154-43b8-bff3-0cb3ebe53934@gmail.com> 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 Sun, Apr 19, 2026 at 02:04:34PM -0400, Andres Freund wrote: > Hi, > > On 2026-04-19 13:53:08 -0400, Bruce Momjian wrote: > > The text I put in the wiki, which I have followed for years, says: > > > > https://wiki.postgresql.org/wiki/Creating_Major_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. > > > > I didn't think +12-17% for an index build would enable new workloads. > > If you want to relitigate that, you are welcome to do so. If this is > > changed, it has to be done so consistently, not just for this item. > > Just about everyone has disagreed vehemently with you about this, in every of > the last 5 releases or so. I don't think it's ok that you continue to ignore > that. That is not my recollection, and I thought I would have heard more about it if that was the case. > I find this policy so depressing that I stopped even opening the release > notes, just to preserve whatever semblance of sanity I possess. I'm know I'm > not alone in that. Well, I just merged the wiki text to explain that we have to consider how much an item is of interest when adding it: While the major release notes include changes to the documented extension interface, it does not include all changes of interest to extension developers or Postgres forks because doing so would include too many items that would be uninteresting to the general audience. 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, if you want to change this process, please feel free to get agreement on new text that I can follow, or someone else can follow. I have always hesitated to expand the list of items with concern that general Postgres users will lose interest in reading it. I have in mind that the release notes are not for me or hackers subscribers to read. I think we expanded the the list for optimizer changes. Could we find a way to do that more that would be readable? I don't know. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.