Re: PG 18 release notes draft committed - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PG 18 release notes draft committed
Date
Msg-id aEneJEgapEJvV8KU@momjian.us
Whole thread Raw
In response to Re: PG 18 release notes draft committed  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Wed, Jun 11, 2025 at 02:45:58PM -0400, Melanie Plageman wrote:
> On Thu, May 29, 2025 at 12:41 PM Bruce Momjian <bruce@momjian.us> wrote:
> >
> > On Thu, May 29, 2025 at 09:42:30AM -0400, Melanie Plageman wrote:
> > > > > "Add an asynchronous I/O subsystem"
> > > I noticed in the PG 17 release notes [1] we did include the shas of
> > > each of the commits for the read stream users. Should we do that here
> > > as well? Those are what enable those operations to use AIO.
> >
> > So, I added the read stream item to PG 17 since that was a new
> > infrastructure feature, but for PG 18, we are just improving that
> > internal infrastructure, so didn't mention it.  If you think we should
> > add those commits, I can do it.
> 
> I wouldn't consider it as improving internal infrastructure exactly.
> My understanding is that usually when we add new features, even if
> they use an existing API, we still include them, as relevant, in the
> release notes. For example, next release we hope to have index
> prefetching -- but it may be implemented using the read stream API.
> Does that mean we wouldn't mention it in the release notes?

We certainly would mention index prefetching, but probably not the
changes to the read stream API unless those were separately relevant.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUG] Cannot flush buffers of temp table deleted from other session
Next
From: Nathan Bossart
Date:
Subject: Re: add function for creating/attaching hash table in DSM registry