Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lijuS-0001Bp-2l for pgsql-hackers@arkaria.postgresql.org; Mon, 17 May 2021 20:32:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lijuR-0002as-1v for pgsql-hackers@arkaria.postgresql.org; Mon, 17 May 2021 20:32:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lijuQ-0002ak-Qn for pgsql-hackers@lists.postgresql.org; Mon, 17 May 2021 20:32:14 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lijuO-0007Sv-7L for pgsql-hackers@postgresql.org; Mon, 17 May 2021 20:32:14 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1lijuJ-0002hl-Vg; Mon, 17 May 2021 16:32:07 -0400 Date: Mon, 17 May 2021 16:32:07 -0400 From: Bruce Momjian To: Peter Geoghegan Cc: Fujii Masao , PostgreSQL-development Subject: Re: PG 14 release notes, first draft Message-ID: <20210517203207.GA32199@momjian.us> References: <20210510060308.GC6088@momjian.us> <87b60661-750a-163c-d15c-2f1248235583@oss.nttdata.com> <20210517134504.GJ24531@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, May 17, 2021 at 12:45:44PM -0700, Peter Geoghegan wrote: > I propose that the B-Tree index item (bottom-up index deletion, "Allow > btree index additions to remove expired index entries to prevent page > splits") link back to the documentation for those that want to drill > down: > > https://www.postgresql.org/docs/14/btree-implementation.html#BTREE-DELETION > > The same approach was used for the Postgres 13 B-Tree deduplication > release note item (same page from the docs, even). > > I understand that it's kind of hard to get the point of the feature > across within the confines of the release notes, which have a very > wide audience. I believe that the practical take-away for more > experienced users should be something like "significantly ameliorates > write-amplification problems in indexes with non-HOT updates". But > that's quite a mouthful. Having a hyperlink to the docs seems like a > sensible compromise. I really just want experienced users to be able > to make the connection between this feature and well-publicized > problems with Postgres index bloat/VACUUM. Yes, I am going to add links to everything, but haven't had time yet. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.