From: Bruce Momjian <bruce@momjian.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 14 release notes, first draft
Date: Mon, 17 May 2021 16:32:07 -0400
Message-ID: <20210517203207.GA32199@momjian.us> (raw)
In-Reply-To: <CAH2-Wz=sQV+p2A_xMh5piGg=3MnXMsG8451dbxjPjz8B4c1vJA@mail.gmail.com>
References: <20210510060308.GC6088@momjian.us>
<87b60661-750a-163c-d15c-2f1248235583@oss.nttdata.com>
<20210517134504.GJ24531@momjian.us>
<CAH2-Wz=sQV+p2A_xMh5piGg=3MnXMsG8451dbxjPjz8B4c1vJA@mail.gmail.com>
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 <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, pg@bowt.ie, masao.fujii@oss.nttdata.com
Subject: Re: PG 14 release notes, first draft
In-Reply-To: <20210517203207.GA32199@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox